[JIRA] [core] (JENKINS-24752) NodeProvisioner algorithm is suboptimal for fast one-off cloud

7 views
Skip to first unread message

scm_issue_link@java.net (JIRA)

unread,
Jul 30, 2015, 2:58:01 PM7/30/15
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on Bug JENKINS-24752
 
Re: NodeProvisioner algorithm is suboptimal for fast one-off cloud

Code changed in jenkins
User: Jesse Glick
Path:
demo/run.sh
http://jenkins-ci.org/commit/parallel-test-executor-plugin/f11a8e4f47bfe0b1fd935d4cff913e1d70c2e55f
Log:
JENKINS-24752 Noting.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

scm_issue_link@java.net (JIRA)

unread,
Aug 5, 2015, 8:28:01 AM8/5/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Jesse Glick
Path:
demo/run.sh

http://jenkins-ci.org/commit/workflow-plugin/81283c06e02f128e6c5abe774e08ed0e74e5740d
Log:
JENKINS-24752 Speeding up cloud slave provisioning for this relatively quick-running demo.

nicolas.deloof@gmail.com (JIRA)

unread,
Oct 5, 2015, 2:01:06 PM10/5/15
to jenkinsc...@googlegroups.com

For docker-slaves we decided to just bypass the Cloud API.
A container-based environment doesn't rely on re-used executors, so using a RetentionStrategy doesn't make sense, as to wait for any delay before provisioning a container for the build. We actually listen to the Queue for the onEntered event, which is a clear signal a build do require an executor, and add a unique label to ensure this container-executor will only be used by this specific job. This has various side effects (especially when container fails to run) that we haven't addressed yet. As the container image is defined by the job I'd like the build to still run (on a fake executor?) but get result set as NOT_BUILT with the container startup log attached.

gentoo.integer@gmail.com (JIRA)

unread,
Oct 5, 2015, 2:11:01 PM10/5/15
to jenkinsc...@googlegroups.com

vincent@latombe.net (JIRA)

unread,
Jun 24, 2019, 4:32:03 AM6/24/19
to jenkinsc...@googlegroups.com
Vincent Latombe started work on Bug JENKINS-24752
 
Change By: Vincent Latombe
Status: Open In Progress
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

vincent@latombe.net (JIRA)

unread,
Jun 24, 2019, 4:32:03 AM6/24/19
to jenkinsc...@googlegroups.com

vincent@latombe.net (JIRA)

unread,
Jun 24, 2019, 4:32:04 AM6/24/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 15, 2019, 6:29:05 AM7/15/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated Bug JENKINS-24752
 

It was released in Jenkins 2.185

Change By: Oleg Nenashev
Status: In Review Resolved
Resolution: Fixed
Released As: Jenkins 2.185
Reply all
Reply to author
Forward
0 new messages