[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders No - just wanted to be sure I wasn't missing something important If you check the console in from (right click -> inspect element -> console) then it may show something more helpful. could well be a network thing, but would be good to know what that is as all things are solvable There is a bunch of work going on speeding up things too, so that may help, but would be good to know what this is. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38362) Poll on a full clone on master, shallow clone using refspec on slaves
Title: Message Title Mark Waite commented on JENKINS-38362 Re: Poll on a full clone on master, shallow clone using refspec on slaves That's a good suggestion and is very similar to something that is implemented in the Mercurial plugin. The Mercurial plugin clones a copy of the mercurial repository to the master, then uses the Jenkins client / server protocol to deliver the repository to individual agents. Unfortunately, that technique has not been implemented for the git plugin. You might be able to get most of the benefit of that technique by referring to my "Jenkins hints for large git repos" from Jenkins World 2016. In particular, a reference repository can dramatically reduce the clone time and the disc use of a repository. I've used it with 18 GB git repositories quite successfully. The other potential significant win is if you can use a sparse checkout to narrow the directories you checkout to the working directory. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38362) Poll on a full clone on master, shallow clone using refspec on slaves
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38362 Poll on a full clone on master, shallow clone using refspec on slaves Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9131) use security group to count instances launched by jenkins
Title: Message Title rob p commented on JENKINS-9131 Re: use security group to count instances launched by jenkins Here's anouther downside of using the ami id rather than using a known tag that i've just discovered. If you change the ami being pointed to (say, every time you rebuild the ami image for your slave workers) you'll get the instance cap for that ami in addition to all the existing slaves which use the older ami. The net result is (in my case) the slave count being higher than the actual instance cap set causes knock on problems elsewhere in the infrastructure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Michael Neale commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action Ryan Campbell we were talking about this - is already done. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title tik dik commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum download the hpi file, and in manage plugins advance tab ,upload the file install. before install ,need install analysis-core plugin manual upload. i have to install plugin manual Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title tik dik edited a comment on JENKINS-32796 Re: Can't update plugins: incorrect checksum my jenkins version 2.19, still have the same issuePreparation Checking internet connectivityChecking update center connectivityjava.net.MalformedURLException: no protocol: at java.net.URL.(URL.java:593) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at hudson.model.UpdateCenter$UpdateCenterConfiguration.toUpdateCenterCheckUrl(UpdateCenter.java:1059) at hudson.model.UpdateCenter$UpdateCenterConfiguration.checkUpdateCenter(UpdateCenter.java:1045) at hudson.model.UpdateCenter$ConnectionCheckJob.run(UpdateCenter.java:1477) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745)xUnit plugin Failure - DetailsStatic Analysis Utilities Failure - DetailsPMD Plug-in Failure - DetailsStatic Analysis Utilities SuccessCheckstyle Plug-in Failure -java.io.IOException: Downloaded file /var/lib/jenkins/plugins/checkstyle.jpi.tmp does not match expected SHA-1, expected 'xapio8iSEkCFTYeIaD5R/N9ViYw=', actual 'oedAya3U0wtIaVcj7GhqGzy5dZU=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1799) at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1950) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1669) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1864) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) $:~/Web$ cat /var/lib/jenkins/plugins/checkstyle.jpi.tmp302 FoundFoundThe document has moved here. Add Comment This message was sent by
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Keith Zantow edited a comment on JENKINS-38363 Re: Investigate slow loading experience [~michaelneale] I looked at this last week, the issue is mostly due to the API times. After some discussion with [~ coervivek vivek ] fetching all the data using the traditional Jenkins object model results in reading a lot of data from disk, potentially including all the runs for all the jobs and more to find the latest and branch count, etc.. At a minimum, we can restrict it to the page asked for, ideally we can use some other optimizations to speed it up significantly more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title tik dik commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum my jenkins version 2.19, still have the same issue Preparation Checking internet connectivity Checking update center connectivity java.net.MalformedURLException: no protocol: at java.net.URL.(URL.java:593) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at hudson.model.UpdateCenter$UpdateCenterConfiguration.toUpdateCenterCheckUrl(UpdateCenter.java:1059) at hudson.model.UpdateCenter$UpdateCenterConfiguration.checkUpdateCenter(UpdateCenter.java:1045) at hudson.model.UpdateCenter$ConnectionCheckJob.run(UpdateCenter.java:1477) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) xUnit plugin Failure - Details Static Analysis Utilities Failure - Details PMD Plug-in Failure - Details Static Analysis Utilities Success Checkstyle Plug-in Failure - java.io.IOException: Downloaded file /var/lib/jenkins/plugins/checkstyle.jpi.tmp does not match expected SHA-1, expected 'xapio8iSEkCFTYeIaD5R/N9ViYw=', actual 'oedAya3U0wtIaVcj7GhqGzy5dZU=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1799) at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) at hudson.model.UpdateCenter$InstallationJob.replace(UpdateCenter.java:1950) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1194) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1669) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1864) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1640) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale commented on JENKINS-38363 Re: Investigate slow loading experience Keith Zantow good to know, yes I suspected. Maybe shoudl leave this open as a place holder for any other investiation related to JENKINS-38253 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang closed an issue as Fixed Jenkins / JENKINS-38262 Jenkins can't visit update-center Change By: binhui wang Status: Open Closed Assignee: Oleg Nenashev binhui wang Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38262) Jenkins can't visit update-center
Title: Message Title binhui wang commented on JENKINS-38262 Re: Jenkins can't visit update-center I have resloved the problem; Replace the default url in file hudson.model.UpdateCenter.xml to the appointed url ; Just like：https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38195) Jenkins available plugin list is emtpy
Title: Message Title ye shengfei assigned an issue to Unassigned Jenkins / JENKINS-38195 Jenkins available plugin list is emtpy Change By: ye shengfei Assignee: ye shengfei Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Ed Sherwin Nonog commented on JENKINS-32118 Re: Opening Robot Framework log failed Gurpreet Singh This works for me. Thanks a lot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Keith Zantow edited a comment on JENKINS-38363 Re: Investigate slow loading experience [~michaelneale] I looked at this last week, the issue is mostly due to the API times. After some discussion with [~coervivek] fetching all the data using the traditional Jenkins object model results in reading a lot of data from disk, potentially including all the runs for all the jobs and more to find the latest and branch count, etc.. At a minimum, we can restrict it to the page asked for, ideally we can use some other optimizations to speed it up significantly more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Dan Dillingham Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Daniel Dan Dillingham Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Daniel Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Daniel Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Keith Zantow commented on JENKINS-38363 Re: Investigate slow loading experience Michael Neale I looked at this last week, the issue is mostly due to the API times. After some discussion with Vivek Panday fetching all the data using the traditional Jenkins object model results in reading a lot of data from disk, potentially including all the runs for all the jobs to find the latest and branch count, etc.. At a minimum, we can restrict it to the page asked for, ideally we can use some other optimizations to speed it up significantly more. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38253) Optimize static resource fetch
Title: Message Title Michael Neale commented on JENKINS-38253 Re: Optimize static resource fetch Keith Zantow was also going to take a look at this with Tom Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38253) Optimize static resource fetch
Title: Message Title Michael Neale commented on JENKINS-38253 Re: Optimize static resource fetch Cliff Meyers it is generated on startup (the hash) - so each restart will make things reload Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale commented on JENKINS-38363 Re: Investigate slow loading experience Keith Zantow if you could also take a look at https://issues.jenkins-ci.org/browse/JENKINS-38253 to help tom out, that would be appreciated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale assigned an issue to Keith Zantow Jenkins / JENKINS-38363 Investigate slow loading experience Change By: Michael Neale Assignee: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38363 Investigate slow loading experience Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/20 1:35 AM Priority: Critical Reporter: Michael Neale When loading dogfood, or even locally, there is a noticable slowness in loading (can be seen as worm takes a while to cross the screen): This could be the result of the search api slowness (being addressed) or perhaps static resource inefficiencies: https://issues.jenkins-ci.org/browse/JENKINS-38253 Investigating the causes of this (to confirm those other tickets) makes sense. Add Comment
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38363 Investigate slow loading experience Change By: Michael Neale Sprint: 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38362) Poll on a full clone on master, shallow clone using refspec on slaves
Title: Message Title Eli White created an issue Jenkins / JENKINS-38362 Poll on a full clone on master, shallow clone using refspec on slaves Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2016/Sep/20 1:25 AM Priority: Minor Reporter: Eli White We have a large git repo with lots of history and lots of branches. As of https://issues.jenkins-ci.org/browse/JENKINS-31393, we can now specify a refspec and have the initial fetch respect it. We have two jobs for each repo. One that builds master, and one that builds everything except master. Specifying a refspec works for our master job, but won't for the feature branches job since it needs to be able to fetch more than just the specified refspec. However, a shallow clone of all branches is too expensive and takes about 18 minutes to complete from inside the datacenter that contains our git repo. It seems like the ideal is for the master to have a full clone of our repo to be able to do polling and figure out what branch / revision to build, and then for it to tell a slave what revision to do a shallow checkout using a full refspec so it only checks out that one branch. Add Comment
[JIRA] (JENKINS-38087) initial search call extremely slow
Title: Message Title Michael Neale closed an issue as Duplicate Ben Walding vivek has a fix in progress on the linked ticket - once that is in (he is verifying with dogfood workspace locally) - might get you to try again, and re-open this if it is still a problem. Basically pagination was still causing full calculations, thrashing disk. This would make things worse after warm up naturally so hopefully it will address both the unacceptably slow load for page of data, and the warm up. Jenkins / JENKINS-38087 initial search call extremely slow Change By: Michael Neale Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36896) Stack Trace on startup
Title: Message Title Ben Stewart commented on JENKINS-36896 Re: Stack Trace on startup I am also getting this issue? Does anyone have a workaround for this? E.g. creating new symlinks or installing a previous version of Multi-Branch plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38335 Search API too slow for dashboard Change By: Michael Neale *Search API (page limit 26)** Took 7 sec on average (in other cases, 12seconds for 11kb of data - from [~bwalding])* To address sorting by name and exclude certain items from flattening all possible items are loaded in memory** jenkins.getAllItems()** Exclude items that are children of multi-branch and matrix project** Don’t see how we can avoid it unless the jobs are stored in some kind of db with indexed column to speed up sorting and only give limited records instead of all* new PipelineContainerImpl().getPipelines(items) should be pagination aware* At present it creates BluePipeline object for all possible items (ouch!) Also: check that runs/activity benefits from same pagination aware optimisation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-36888) Move non-JDL styles out of JDL and cleanup unneeded styles
Title: Message Title Michael Neale assigned an issue to Josh McDonald Jenkins / JENKINS-36888 Move non-JDL styles out of JDL and cleanup unneeded styles Change By: Michael Neale Assignee: Josh Taylor McDonald Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36888) Move non-JDL styles out of JDL and cleanup unneeded styles
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36888 Move non-JDL styles out of JDL and cleanup unneeded styles Change By: Michael Neale Summary: Move non-JDL styles out of JDL and cleanup unneeded styles Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36888) Move non-JDL styles out of JDL
Title: Message Title Michael Neale assigned an issue to Josh Taylor Jenkins / JENKINS-36888 Move non-JDL styles out of JDL Change By: Michael Neale Assignee: Michael Neale Josh Taylor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38361) Developing blue ocean on windows
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38361 Developing blue ocean on windows Issue Type: Bug Assignee: Keith Zantow Components: blueocean-plugin Created: 2016/Sep/19 11:28 PM Priority: Minor Reporter: Michael Neale Keith has been looking at the problems with browserify and developing on windows (result of hack fest) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38361) Developing blue ocean on windows
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38361 Developing blue ocean on windows Change By: Michael Neale Sprint: 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey commented on JENKINS-38335 Re: Search API too slow for dashboard Michael Neale https://issues.jenkins-ci.org/browse/JENKINS-38087 is duplicate, one of them should be closed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Michael Neale commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Thorsten Scherler are you able to try this branch: https://github.com/jenkinsci/blueocean-plugin/tree/vivek-sse-missing-stage-event-fix with this fix - see if it helps? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38360) Not receiving enough events (SSE) for block scoped stages
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-38360 Not receiving enough events (SSE) for block scoped stages Change By: Michael Neale Assignee: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38360) Not receiving enough events (SSE) for block scoped stages
Title: Message Title Vivek Pandey commented on JENKINS-38360 Re: Not receiving enough events (SSE) for block scoped stages Tom FENNELLY New stages are labels so presence of StageAction is not going to work. I have put a tentative fix in https://github.com/jenkinsci/blueocean-plugin/commit/79ec8ed2b156218451aad6b3e6711639e8e52adc. Tom FENNELLYI have not tested it so there might be other nuances but as far as I see this should fix this issue. Thorsten Scherler if you like please test vivek-sse-missing-stage-event-fix branch with this fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37962 REGRESSION: parallel karaoke not allowing branch selection or completing correctly Change By: Vivek Pandey Comment: [~tfennelly] New stages are labels so presence of StageAction is not going to work. I have put a tentative fix in https://github.com/jenkinsci/blueocean-plugin/commit/79ec8ed2b156218451aad6b3e6711639e8e52adc. [~tfennelly] I have not tested it so there might be other nuances but as far as I see this should fix this issue.[~tscherler] if you like please test vivek-sse-missing-stage-event-fix branch with this fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38136) Support POST requests to the /blue/rest/classes/?q= endpoint
Title: Message Title Vivek Pandey updated JENKINS-38136 Jenkins / JENKINS-38136 Support POST requests to the /blue/rest/classes/?q= endpoint Change By: Vivek Pandey Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37024) Opening the result modal should open over the existing content
Title: Message Title Josh McDonald commented on JENKINS-37024 Re: Opening the result modal should open over the existing content James Dumay I'll put off my work on dialogs and popups until this is done. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Vivek Pandey commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Tom FENNELLY New stages are labels so presence of StageAction is not going to work. I have put a tentative fix in https://github.com/jenkinsci/blueocean-plugin/commit/79ec8ed2b156218451aad6b3e6711639e8e52adc. Tom FENNELLY I have not tested it so there might be other nuances but as far as I see this should fix this issue. Thorsten Scherler if you like please test vivek-sse-missing-stage-event-fix branch with this fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36888) Move non-JDL styles out of JDL
Title: Message Title Josh McDonald commented on JENKINS-36888 Re: Move non-JDL styles out of JDL I suggest Dashboard as a new home for the pipeline renderer, rather than the editor. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Thanks I will try the newer betas. Checking console when refreshing window it flashes an error that was too quick to read, but I captured the frame from a gif. Seems to be a 400 when getting the job path. I had truncated the screen on purpose. Was there something you were hoping to see that wasnt included? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: 400_error.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: console_error.gif Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: console_error.gif Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30910) Job parameters should be exposed as environment variables
Title: Message Title Jesse Glick updated JENKINS-30910 Jenkins / JENKINS-30910 Job parameters should be exposed as environment variables Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30910) Job parameters should be exposed as environment variables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30910 Re: Job parameters should be exposed as environment variables Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/219fde38743eccc3c91cdd32f3061645583d8314 Log: [FIXED JENKINS-30910] Build environment should include parameters. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38079) Investigate performance degradation report
Title: Message Title Michael Neale commented on JENKINS-38079 Re: Investigate performance degradation report see also: https://issues.jenkins-ci.org/browse/JENKINS-38335 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Michael Neale commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Thorsten Scherler vivek and tom will take a look at: https://issues.jenkins-ci.org/browse/JENKINS-38360 - and see if it can be corrected there, as that seems to be blocking this for now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38360) Not receiving enough events (SSE) for block scoped stages
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38360 Not receiving enough events (SSE) for block scoped stages Change By: Michael Neale Sprint: 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/c10a8caa907e2452c83f2ef7fa54d81c6ac70654 Log: Merge pull request #61 from jglick/WORKSPACE-JENKINS-33511 JENKINS-33511 Doc update Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/b5b1ed0d06aa...c10a8caa907e
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/b6fd3093c0cfb962f6562ec30b51efa500c721f3 Log: JENKINS-33511 $WORKSPACE and $NODE_LABELS are now available.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38359) Not receiving enough events (SSE) for block scoped stages
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38359
Not receiving enough events (SSE) for block scoped stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Sep/19 10:25 PM
Priority:
Blocker
Reporter:
Michael Neale
When using the new block scoped stages, SSE events do not arrive correctly. Using the pipeline below, the following events are received: https://issues.jenkins-ci.org/secure/attachment/34010/34010_Screenshot+from+2016-09-19+16-59-36.png however, when non block scoped stages are used, the following events arrive: https://issues.jenkins-ci.org/secure/attachment/34012/34012_Screenshot+from+2016-09-19+17-00-51.png Note that the new syntax is missing stage_id.
node {
stage("hey") {
sh 'ping -c 5 www.apple.com'
}
stage("par") {
parallel (
"b1" : {
sh 'ping -c 2 www.apple.com'
},
"b2" : {
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
}
)
}
stage("ho") {
sh 'ping -c 10 www.apple.com'
}
}
[JIRA] (JENKINS-38360) Not receiving enough events (SSE) for block scoped stages
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-38360
Not receiving enough events (SSE) for block scoped stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Sep/19 10:25 PM
Priority:
Blocker
Reporter:
Michael Neale
When using the new block scoped stages, SSE events do not arrive correctly. Using the pipeline below, the following events are received: https://issues.jenkins-ci.org/secure/attachment/34010/34010_Screenshot+from+2016-09-19+16-59-36.png however, when non block scoped stages are used, the following events arrive: https://issues.jenkins-ci.org/secure/attachment/34012/34012_Screenshot+from+2016-09-19+17-00-51.png Note that the new syntax is missing stage_id.
node {
stage("hey") {
sh 'ping -c 5 www.apple.com'
}
stage("par") {
parallel (
"b1" : {
sh 'ping -c 2 www.apple.com'
},
"b2" : {
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
sh 'sleep 1 && ping -c 1 www.apple.com'
}
)
}
stage("ho") {
sh 'ping -c 10 www.apple.com'
}
}
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Justin Rainwater there are some newer betas out - might be worth trying. Unfortunately in that gif it seems that part of the screen is truncated. Are there any console errors in the browser when you open it in a new tab? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38347) Github plugin dependency sporadically fails with NPE during tests
Title: Message Title Kanstantsin Shautsou assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-38347 Github plugin dependency sporadically fails with NPE during tests Change By: Kanstantsin Shautsou Assignee: Kirill Merkushev Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38358) resource leak in cache?
Title: Message Title Kanstantsin Shautsou assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-38358 resource leak in cache? Change By: Kanstantsin Shautsou Assignee: Kirill Merkushev Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38358) resource leak in cache?
Title: Message Title
Kanstantsin Shautsou updated an issue
Jenkins / JENKINS-38358
resource leak in cache?
Change By:
Kanstantsin Shautsou
{CODE}java.io.IOException: Unable to delete file: C:\Users\XXX\AppData\Local\Temp\hudson2592457631282151845test\org.jenkinsci.plugins.github.GitHubPlugin.cache\78a5c95e\journal{CODE}Current okhttp library version has not closed {{Cache}} that contains closeable {{cache}}. Update to newer version that has autocloseable https://github.com/square/okhttp/commit/d662c1a82851800c46ad8ede2d9d10d10427fdad and close it somewhere
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38358) resource leak in cache?
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-38358 resource leak in cache? Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Sep/19 10:09 PM Priority: Minor Reporter: Kanstantsin Shautsou java.io.IOException: Unable to delete file: C:\Users\XXX\AppData\Local\Temp\hudson2592457631282151845test\org.jenkinsci.plugins.github.GitHubPlugin.cache\78a5c95e\journal Current okhttp library version has not closed Cache that contains closeable cache. Add Comment
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
Christophe ROGER edited a comment on JENKINS-38190
Re: Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Same problem here. Unable to deploy on production using jenkins because of this. Please help us.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38309) Make ForkScanner return Parallel Branches in same order as others
Title: Message Title Sam Van Oort started work on JENKINS-38309 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38309) Make ForkScanner return Parallel Branches in same order as others
Title: Message Title Sam Van Oort updated JENKINS-38309 Jenkins / JENKINS-38309 Make ForkScanner return Parallel Branches in same order as others Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38190) Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Title: Message Title
Christophe ROGER commented on JENKINS-38190
Re: Repository Connector fail to recuperate the parameter ${version} from maven repsitory artifact
Same problem here. Unable to deploy on production using jenkins because of this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title Jesse Glick commented on JENKINS-35184 Re: Failed to load jenkins.util.SystemProperties on slaves due to ServletContext Implementing JENKINS-26677 would probably have made this bug immediately apparent, perhaps in core functional tests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28339) Allow skip-vote to also skip vote for "Started"
Title: Message Title Thanh Ha commented on JENKINS-28339 Re: Allow skip-vote to also skip vote for "Started" Jenkins will remove a vote on started. See:I was able to reproduced with gerrit-trigger 2.22.0. Some steps to reproduce on a fresh Jenkins system: 1. Install Gerrit Trigger plugin 2. Setup Gerrit Trigger plugin server configuration 3. Setup a job to vote Verified+1 when job passes 4. Run job 5. Reconfigure job to skip vote for all available categories: Job Configuration > Gerrit Event > Advanced > Skip Vote on Successful, Failed, Unstable, Not Built 6. Rerun job 7. Gerrit Trigger removes the Verified+1 vote when job starts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28339) Allow skip-vote to also skip vote for "Started"
Title: Message Title Thanh Ha updated an issue Jenkins / JENKINS-28339 Allow skip-vote to also skip vote for "Started" Change By: Thanh Ha Attachment: skip-vote.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37622) Jenkins crash on TestResult trend chart show
Title: Message Title Qi Fan commented on JENKINS-37622 Re: Jenkins crash on TestResult trend chart show Hi Tomasz Mysliwiec, Which java version did you change to? I get the same TestResult trend crash using this version: openjdk version "9-internal" OpenJDK Runtime Environment (build 9-internal+0-2016-04-14-195246.buildd.src) OpenJDK 64-Bit Server VM (build 9-internal+0-2016-04-14-195246.buildd.src, mixed mode) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38357) Cannot use Jenkins Node properties as load directory for Team Concert plugin
Title: Message Title
Rob Leach created an issue
Jenkins / JENKINS-38357
Cannot use Jenkins Node properties as load directory for Team Concert plugin
Issue Type:
Improvement
Assignee:
Unassigned
Components:
teamconcert-plugin
Created:
2016/Sep/19 9:08 PM
Environment:
Jenkins 1.656 Team-concert 1.2.0.1
Labels:
plugin build
Priority:
Major
Reporter:
Rob Leach
There is no way to specify a predefined Node property environment variable as the Load directory for a build job using RTC source code management. So if you have multiple build nodes, you can't defined lets say: SRC_BASE uniquely for each node and then consume that Node property environment variable in a build job, so that the build job could execute on any node available. Some details; we have two linux hosts and two windows hosts setup as a build farm. These four hosts are configured as individual nodes in Jenkins. We want to configure our build jobs so they can run on any node. But there is no way to tell team concert to load to a location on the host that is platform independent. So if node1 was configured with a node property environment variable SRC_BASE=/opt/rtc/ssd and node2 was configured with a node property environment variable SRC_BASE=c:/common/rtc. Then I should be able to configure my build job to use the load directory $ {SRC_BASE}/productname. This currently does not work as it treats ${SRC_BASE} as a string and appends that to the default load directory location.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sam Van Oort stopped work on JENKINS-33185 Change By: Sam Van Oort Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38300) REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying
Title: Message Title Keith Zantow updated JENKINS-38300 Jenkins / JENKINS-38300 REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying Change By: Keith Zantow Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly The new syntax is missing the stage_id. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sam Van Oort commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Piotr Zegar Do you mean the Blue-Ocean plugin? Stage View? Pipeline view plugin? Build Pipeline Plugin? These are all different things. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Daniel Beck commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum Probably what's described more accurately in recent comments to JENKINS-8028 – likely Chinese mirror weirdness. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8028) Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success.
Title: Message Title Daniel Beck commented on JENKINS-8028 Re: Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success. What's the output of e.g. curl -L -I https://updates.jenkins-ci.org/latest/groovy-events-listener-plugin-master.hpi from a machine that gets served the same mirror? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Piotr Zegar commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I see 2 issues with that plugin in latest version: 1. Step time is invalid, like it stop counting when all paraell tasks are started, it looks like step finish but in real job is still waiting for finish of parallel taks until move to next step. 2. No option to scroll to see older builds, it shows only last ~20, but cannot see older one. Would be nice to see same info when entering a specific build page. Except that, I like it.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Daniel Beck resolved as Not A Defect Still not a defect in Jenkins. Probably a misconfigured internet connection, a (temporarily?) bad mirror, or an MITM attack. Not a bug in Jenkins (the bug was that checksums weren't verified for a long time). And for infra issues to investigate, you don't provide enough information, e.g. which mirror is used. Jenkins / JENKINS-32796 Can't update plugins: incorrect checksum Change By: Daniel Beck Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Liam Newman commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
Jesse Glick That doesn't sound like it is fixed then. If what you describe is true, shouldn't that "withEnv" be added to the node method in the core implementation? That would provide the "env.WORKSPACE" that the original description requested.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title
Daniel Spilker closed an issue as Fixed
This is already supported through the Automatically Generated DSL:
job('example') {
publishers {
androidApkUpload {
// ...
}
}
}
Jenkins / JENKINS-38349
Add DSL support for Google Play Android Publisher Plugin
Change By:
Daniel Spilker
Status:
Open Closed
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-38349 Add DSL support for Google Play Android Publisher Plugin Change By: Daniel Spilker Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title
Daniel Spilker resolved as Fixed
This is already supported by the Automatically Generated DSL:
job('example') {
publishers {
awsDeviceFarmRecorder {
projectName('example')
devicePoolName('example')
appArtifact('example')
runName('example')
testToRun('example')
storeResults(true)
isRunUnmetered(true)
eventCount('example')
eventThrottle('example')
seed('example')
username('example')
password('example')
appiumJavaJUnitTest('example')
appiumJavaTestNGTest('example')
appiumPythonTest('example')
calabashFeatures('example')
calabashTags('example')
calabashProfile('example')
junitArtifact('example')
junitFilter('example')
uiautomatorArtifact('example')
uiautomatorFilter('example')
uiautomationArtifact('example')
xctestArtifact('example')
xctestUiArtifact('example')
ignoreRunError(true)
}
}
}
Jenkins / JENKINS-38351
Add job DSL script support for aws device farm plugin
Change By:
Daniel Spilker
Status:
Open Resolved
Resolution:
Fixed
Add Comment
[JIRA] (JENKINS-38356) Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges
Title: Message Title lucas Pessoa created an issue Jenkins / JENKINS-38356 Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges Issue Type: Improvement Assignee: Jesse Glick Components: matrix-auth-plugin Created: 2016/Sep/19 7:59 PM Environment: Jenkins 1.609.1 Matrix Authorization Strategy 1.4 Icon Shim 2.0.3 cloudbees-folder 5.12 credentials 2.14 Priority: Major Reporter: lucas Pessoa We are using the Matrix Authorization Strategy Plugin 1.4 We want a majority of our users to have certain permissions such as viewing, building, and configuring our over one hundred Jenkins jobs. However there are certain jobs we want to limit so that only administrators and certain specified users can have access to them. We have tried using the Block inheritance of global authorization matrix option however this allows users to completely override the administrators permissions. A) Is there anyway so that "Block inheritance of global authorization matrix" does not effect administrators? or B) Is there anyway so that only Admins can add and alter the "Block inheritance of global authorization matrix" field inside the Jenkins jobs? or 3) Is there some other solution for this? Another plugin?
[JIRA] (JENKINS-38356) Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges
Title: Message Title lucas Pessoa updated an issue Jenkins / JENKINS-38356 Matrix Authorization Strategy Plugin - Block inheritance of global authorization matrix - This overrides administrators privileges Change By: lucas Pessoa We are using the +Matrix Authorization Strategy Plugin 1.4+We want a majority of our users to have certain permissions such as viewing, building, and configuring our over one hundred Jenkins jobs.However there are certain jobs we want to limit so that only administrators and certain specified users can have access to them.We have tried using the *Block inheritance of global authorization matrix* option however this allows users to completely override the administrators permissions.*A)* Is there anyway so that "Block inheritance of global authorization matrix" does not effect administrators? *or**B)* Is there anyway so that only Admins can add and alter the "Block inheritance of global authorization matrix" field inside the Jenkins jobs?*or** 3 C )* Is there some other solution for this? Another plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37741) gitlab oauth plugin:GitlabAPIException
Title: Message Title Mohamed EL Habib resolved as Fixed fixed into 1.0.9 version Jenkins / JENKINS-37741 gitlab oauth plugin:GitlabAPIException Change By: Mohamed EL Habib Status: Reopened Resolved Assignee: Jairo Ricarte Ye Deming Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-38351 Add job DSL script support for aws device farm plugin Change By: Daniel Spilker Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37834) Spacing and alignment of "action" icons is inconsistent
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37834 Spacing and alignment of "action" icons is inconsistent Change By: Cliff Meyers The "action" icons on the right side of various tables are often improperly aligned (should be right-aligned) and have inconsistent spacing between the icons. The columns are often much wider than they need to be.Areas to look at:* Pipeline List* Activity tab listing* Branches tab listing* PR's tab listingImpl Notes* Some icons are placed directly into the td element within the Dashboard code.* Other icons (Favorites) are added via an Extensions.Render element* Both containers need to ultimately have the same height and apply some consistent horizontal spacing between the elements* Probably requires some small tweaks to Extensions.Render itself (perhaps just adding support for a className prop)* Column width will be problematic since each they is driven by an absolute width set on TH irrespective of the number of child elements. Ideally this should be flexible, although it may require some rejiggering of the table layouts to be more flexible. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37715 Make gulp builds consistent across main blueocean modules Change By: Cliff Meyers Use js-builder consistently across the following modules:* blueocean-core-js* blueocean-dashboard* blueocean-personalization* jenkins-design-languageOther tasks:* Add karma support to js-builder, make default* [] Publish test report* Consistent lint rules (fix warnings about invalid peer deps for eslint if possible)* Add npm shrinkwrap to ** blueocean-core-js ** (/) blueocean - web, blueocean-dashboard, blueocean-personalization, blueocean-config** (/) And documentation for update process - * Add script to validate package.json vs. npm-shrinkwrap.json (exists for JDL; needs to be added to others) * Possibly add native mocha support as well? Gulp builds in blueocean-dashboard and blueocean-personalization use it but will switch to karma anyways. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37715 Make gulp builds consistent across main blueocean modules Change By: Cliff Meyers Use js-builder consistently across the following modules:* blueocean-core-js* blueocean-dashboard* blueocean-personalization* jenkins-design-languageOther tasks:* Add karma support to js-builder, make default* [] Publish test report* Consistent lint rules (fix warnings about invalid peer deps for eslint if possible)* Add npm shrinkwrap** blueocean-core-js** (/) blueocean-web, blueocean-dashboard, blueocean-personalization, blueocean-config** (/) And documentation for update process* Add script to validate package.json vs. npm-shrinkwrap.json (exists for JDL; needs to be added to others) * Possibly add native mocha support as well? Gulp builds in blueocean-dashboard and blueocean-personalization use it but will switch to karma anyways. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you
[JIRA] (JENKINS-38355) Deleting an Upstream deployment allows a promoted build to continue without approval
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38355 Deleting an Upstream deployment allows a promoted build to continue without approval Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Sep/19 7:34 PM Environment: Jenkins ver. 1.651.3.1 Promoted Builds ver. 2.27 Priority: Major Reporter: Alex Taylor If you have a promoted build waiting on approval from 2 upstream deployments and then delete one of those upstream projects, it will allow the build to be promoted with only approving the other(non-deleted) deployment. Steps to reproduce: -Create 2 upstream projects Project A and B -Create a promoted build(downstream build) that depends on approval of A and B to complete -Run the downstream build -Observe it is waiting on A and B to build and be approved -Build A and B but dont approve either -Delete project A completely -Approve B -Observe the downstream build is completed Expected Results: For security reasons I would think this downstream build would need to be re-built before allowing it to be promoted. Additional thoughts: I would think this would also be reproduced if you only had 1 promoted upstream build that downstream build was waiting on and then deleted the upstream but I have not tested it.
[JIRA] (JENKINS-37715) Make gulp builds consistent across main blueocean modules
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37715 Make gulp builds consistent across main blueocean modules Change By: Cliff Meyers Use js-builder consistently across the following modules:* blueocean-core-js* blueocean-dashboard* blueocean-personalization* jenkins-design-languageOther tasks:* Add karma support to js-builder, make default* Publish test report* Consistent lint rules (fix warnings about invalid peer deps for eslint if possible)* Add shrinkwrap ? to blueocean-core-js - And documentation for update process - * Add script to validate package.json vs. npm-shrinkwrap.json (exists for JDL; needs to be added to others) * Possibly add native mocha support as well? Gulp builds in blueocean-dashboard and blueocean-personalization use it but will switch to karma anyways. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-38350) Unable to build Android app getting Could not expand ZIP error
Title: Message Title Derrik Ammons commented on JENKINS-38350 Re: Unable to build Android app getting Could not expand ZIP error Thanks Chris. I was able to reproduce this with Android Studio. So, it must be some configuration or Gradle setup. Thanks for taking a look. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-38354
Failure to resume a wrapper step leads to hanging build
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
workflow-cps-plugin
Created:
2016/Sep/19 7:16 PM
Labels:
robustness
Priority:
Major
Reporter:
Jesse Glick
Take this PR and comment out optional=true which allows ConsoleLogFilterStep.Execution to be safely restored. Run Jenkins with it, create and attach a JNLP agent, create a Pipeline script running something like
node('agent-name') {
checkout([$class: 'MercurialSCM', source: 'http://hg.netbeans.org/main-silver/'])
ant 'build'
}
(or just any long-running Ant project) and start running. Once it is running Ant, restart Jenkins. After the restart, a bit more output will be printed and then the build will hang, irrecoverably. workflow-durable-task-step PR 17 will allow you to see that there is a Guice-related exception. But after that any attempt to abort the build will simply print an error: the sh step already got stopped, so exited with 143 (SIGTERM), but then the consoleLogFilter step's StepContext thinks it too is already finished, and will not allow it to be finished "again". The virtual thread dump says it is in consoleLogFilter. Only a hard kill suffices at this point. Is there some way to force the CPS VM thread to treat the current StepExecution as a lost cause and really throw its exception up the call stack?
[JIRA] (JENKINS-38223) Incorrect state of completed parallel branch
Title: Message Title Sam Van Oort commented on JENKINS-38223 Re: Incorrect state of completed parallel branch > Rather than asking caller to infer that all has ended since you have this end block, which is true but 'isRunning() API' makes no sense to return true in this case as well. Yeah, it's a clear bug in workflow-cps here. I think fixable, by looking more closely at cases with > 1 currentHead (and then seeing if it's the end of one of the currently executing branch). May be something I can fix as a small one-off fix (probably needs a change in workflow-api and workflow-cps though, due to spec). In pipeline-graph-analysis I use a bit of a deeper inspection to work around this, by looking to see if the node is the BlockEndNode for a BlockStartNode which is a parallel branch start. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones commented on JENKINS-38315 Re: Please wait while Jenkins is getting ready to work Just uploaded package_list which contains the output of rpm -qa if that will help find a missing or down rev package or lib. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones updated an issue Jenkins / JENKINS-38315 Please wait while Jenkins is getting ready to work Change By: andrew jones Attachment: package_list Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Jesse Glick updated JENKINS-33511
Jenkins / JENKINS-33511
env.WORKSPACE should be available within node{} in Pipeline
Change By:
Jesse Glick
Status:
In Review Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones commented on JENKINS-38315 Re: Please wait while Jenkins is getting ready to work As another attempt I've build a VM running scientific linux 7 and installed jdk 8. jdk-8u101-linux-x64.rpm Jenkins did not start. Some other documentation mentioned jna was needed by Hudson so I installed that, still no start. So I went back to some older versions using the following install/uninstall yum erase jenkins shutdown -r now yum install service jenkins start jenkins-1.642.1-1.1.noarch.rpm - working jenkins-1.651.1-1.1.noarch.rpm - working jenkins-1.651.3-1.1.noarch.rpm - working jenkins-2.7.1-1.1.noarch.rpm - not working jenkins-2.9-1.1.noarch.rpm - not working So I went back to my original redhat machine and installed jenkins-1.651.3-1.1.noarch.rpm and it started up fine. I'd installed jna on that so as a test I removed it, rebooted and jenkins started. So something has changed between jenkins-1.651.3-1.1.noarch.rpm and jenkins-2.7.1-1.1.noarch.rpm that seems to only be affecting my servers, it would be interesting to know what it is. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37463) Link to the job out of pipeline stage view
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37463 Link to the job out of pipeline stage view Change By: Sam Van Oort Summary: Link to the job out of Blue Ocean/ pipeline stage view Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Pragya Jaiswal edited a comment on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Thanks Mark. that does resolve my issue. However, how can I extend the functionality of my jenkins job -My jenkins job tracks multiple branches and triggers builds if there are changes to any of those branches. For example I have multiple branch specifiers added to my job -origin/release**origin/developThe job is working fine when there are merges to any of these branches.In some cases I want to be able to specify/input a branch to pull the source and build from. How can I accomplish that considering I have the branch specifiers already set? Any ideas on implementing this?I tried a couple of things -1. Added a build parameters called $BranchOverride and tried 2 test cases. case 1 - Setting the default value to "None" with 3 branch specifiers for release/*, develop and $BranchOverride. Case 2 - setting the default value to origin/develop and set 2 branch specifiers release/* and $BranchOverride. Both the cases, when I manually input a branch, it doesn't work as I expect it to.2. Instead of specifying multiple Branch specifiers, I created a string Parameter $BranchOverride and set the value as a regex : (?=(origin/develop|origin/release)).*When I push to one of my release branch, it triggers a build (and multiple consecutive builds) for multiple branches, even those that dont have any push. I see this is the log -Seen 1,116 remote branchesMultiple candidate revisionsScheduling another build to catch up with ABC_TestJobChecking out Revision 366bdc3674103e4b2479d75508f3971c6f080591 (origin/release/xyz)Maybe I am not understanding the behavior correctly, am not sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Pragya Jaiswal edited a comment on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Thanks Mark. that does resolve my issue. However, how can I extend the functionality of my jenkins job -My jenkins job tracks multiple branches and triggers builds if there are changes to any of those branches. For example I have multiple branch specifiers added to my job -origin/release**origin/developThe job is working fine when there are merges to any of these branches.In some cases I want to be able to specify/input a branch to pull the source and build from. How can I accomplish that considering I have the branch specifiers already set? Any ideas on implementing this?I tried a couple of things -1. Added a build parameters called $BranchOverride and tried 2 test cases. case 1 - Setting the default value to "None" with 3 branch specifiers for release/* , develop and $BranchOverride. Case 2 - setting the default value to origin/develop and set 2 branch specifiers release/ * and $BranchOverride. Both the cases, when I manually input a branch, it doesn't work as I expect it to.2. Instead of specifying multiple Branch specifiers, I created a string Parameter $BranchOverride and set the value as a regex : (?=(origin/develop|origin/release)).*When I push to one of my release branch, it triggers a build (and multiple consecutive builds) for multiple branches, even those that dont have any push. I see this is the log -Seen 1,116 remote branchesMultiple candidate revisionsScheduling another build to catch up with ABC_TestJobChecking out Revision 366bdc3674103e4b2479d75508f3971c6f080591 (origin/release/xyz) I must add that in the test case where I added a regex, manually giving the branch input works but the automated trigger doesnt behave as expected. Maybe I am not understanding the behavior correctly, am not sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
