[JIRA] (JENKINS-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak updated an issue Jenkins / JENKINS-31939 The top value is better to be chosen by default of to have such option Change By: Viachaslau Kabak Attachment: by timer.PNG Attachment: by timer_console.PNG Attachment: manually.PNG Attachment: plugin version.PNG Attachment: plugin_config.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this
[JIRA] (JENKINS-36944) Agent goes offline during the build
Title: Message Title Alexandru Hadar updated an issue Jenkins / JENKINS-36944 Agent goes offline during the build Change By: Alexandru Hadar Summary: Agent goes online offline during the build after 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option I have added my screenshots with plugin version and with 2 types of job run: 1) by timer 2) manually 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Sprint: 1.0-beta-1 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed I'm closing this as I'm quite sure this is an issue that was seen on the dogfood server (how many times have I seen it with out of date plugins etc) and not verified on a clean Jenkins. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY closed an issue as Cannot Reproduce Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Status: Open Closed Resolution: Cannot Reproduce 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-36978) Javascript duplicated in each individual javascript file
Title: Message Title Michael Neale commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file Tom FENNELLY ok - currently its 90K (minified would be probably 9K) gzipped, and Ben Walding personally counts every single bit from his servers. I think he pays by the bit. OK closing out. 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-35669) email-ext-plugin shows HTML entities as plaintext in HTML email output
Title: Message Title Patrick Julian commented on JENKINS-35669 Re: email-ext-plugin shows HTML entities as plaintext in HTML email output Thanks! 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-36978) Javascript duplicated in each individual javascript file
Title: Message Title Michael Neale closed an issue as Won't Fix no body likes ben. Jenkins / JENKINS-36978 _javascript_ duplicated in each individual _javascript_ file Change By: Michael Neale Status: Open Closed Resolution: Won't 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-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36941 Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth Change By: Michael Neale Priority: Critical Major 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-36234) Publish official docker container continuously
Title: Message Title Michael Neale resolved as Won't Fix Jenkins / JENKINS-36234 Publish official docker container continuously Change By: Michael Neale Status: In Progress Resolved Resolution: Won't 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-36650) Why do acceptance tests not run for branches?
Title: Message Title Michael Neale resolved as Won't Fix Jenkins / JENKINS-36650 Why do acceptance tests not run for branches? Change By: Michael Neale Status: In Progress Resolved Resolution: Won't 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-36439) Evolve more composable redux store code patterns
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36439 Evolve more composable redux store code patterns Change By: Michael Neale Priority: Blocker Major 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-36640) Result modal never transitions from running to success/fail (AWOL SSE messages)
Title: Message Title Michael Neale closed an issue as Won't Fix This wasn't tested locally. tickets based only on .io without local verification are not valid and kind of waste everyones time. Jenkins / JENKINS-36640 Result modal never transitions from running to success/fail (AWOL SSE messages) Change By: Michael Neale Status: Open Closed Resolution: Won't 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,
[JIRA] (JENKINS-36986) Jobs with syntactically incorrect config missing the cron spec for a trigger using job-dsl produces NullPointerException
Title: Message Title
Félix Belzunce Arcos created an issue
Jenkins / JENKINS-36986
Jobs with syntactically incorrect config missing the cron spec for a trigger using job-dsl produces NullPointerException
Issue Type:
Bug
Assignee:
Félix Belzunce Arcos
Components:
ghprb-plugin
Created:
2016/Jul/27 7:24 AM
Priority:
Minor
Reporter:
Félix Belzunce Arcos
To re-produce you just need to use the https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin and not use the "cron('H/5 * * * *')" as the documentation says. Then, the following stacktrace is triggered:
Jun 23, 2016 10:35:00 AM hudson.triggers.Trigger$Cron doRun
WARNING: Cron thread throw an exception
java.lang.NullPointerException
at hudson.triggers.Trigger.checkTriggers(Trigger.java:267)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:221)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Any cron job on the instance will work because of this issue
[JIRA] (JENKINS-36638) SSE events not coming through to the client
Title: Message Title Michael Neale closed an issue as Won't Fix Wasn't reproduced locally and likely due to unupdated plugins on dogfood. It is critical to reproduce things locally. If there is a problem with SSE and proxies it shoudl be clear and proven that is the case. Jenkins / JENKINS-36638 SSE events not coming through to the client Change By: Michael Neale Status: In Progress Closed Resolution: Won't 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 unsubscrib
[JIRA] (JENKINS-36177) Acceptance test for Multi-Branch flow
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36177 Acceptance test for Multi-Branch flow Change By: Michael Neale Priority: Blocker Critical 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-36986) Jobs with syntactically incorrect config missing the cron spec for a trigger using job-dsl produces NullPointerException
Title: Message Title Félix Belzunce Arcos started work on JENKINS-36986 Change By: Félix Belzunce Arcos 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-36177) Acceptance test for Multi-Branch flow
Title: Message Title Michael Neale commented on JENKINS-36177 Re: Acceptance test for Multi-Branch flow changed this to not-blocking as it is doesn't have a think linked that it is blocking. Cliff Meyers would like to have good coverage in ATH for these common cases, but not technically blocking. 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-35368) Token Macro Workflow Support
Title: Message Title Pierre CRESSANT assigned an issue to Pierre CRESSANT Jenkins / JENKINS-35368 Token Macro Workflow Support Change By: Pierre CRESSANT Assignee: Alex Earl Pierre CRESSANT 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-36978) Javascript duplicated in each individual javascript file
Title: Message Title Tom FENNELLY commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file I love Ben !!! Michael Neale What exactly is 90K? I'm faiirly sure the duplicate part is way less than that (unminified and ungzipped). 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-36978) Javascript duplicated in each individual javascript file
Title: Message Title Michael Neale commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file 9K is the gzipped size of the overhead, x10 resources = 90K. at least that is what he told me. 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-36978) Javascript duplicated in each individual javascript file
Title: Message Title Tom FENNELLY commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file Okay if Ben says it then I'm sure it's accurate !! There are tradeoffs here and I'd not be in favour of moving these things outside the bundles. If it's a problem then we need to think of other solutions. I want this bootstrap code to be part of the bundle because it's the one thing that the bundle should be able to rely on to be consistent forever (from the time it was built) 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-36941) Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth
Title: Message Title James Dumay commented on JENKINS-36941 Re: Restarting server (or letting session timeout) will cause hidden auth failures rather than trigger reauth This is in scope to fix for the beta - it's a common use case as of Jenkins 2 to have security enabled 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-36439) Evolve more composable redux store code patterns
Title: Message Title Tom FENNELLY closed an issue as Won't Do Closing this as Cliff is already working on introducing MobX in the personalization. Jenkins / JENKINS-36439 Evolve more composable redux store code patterns Change By: Tom FENNELLY Status: Open Closed Resolution: Won't Do 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 option
[JIRA] (JENKINS-36978) Javascript duplicated in each individual javascript file
Title: Message Title Ben Walding commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file You're lucky this is a public JIRA or I'd tell you what I really thought of your lack of care and respect for the contributing community you have. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Tom FENNELLY good to know that this is working! We might want to reopen this - it's not as the designed specified. Missing the "OPEN" link when it says it's queued. 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Boguslaw Klimas commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option It does not work from you because these changes have not yet been merged. I made only pull request, so you can see whether such a change is right for you. At version 0.6.1 will not work, as you want. If you want to use it you must wait to release 0.6.2 or compile plugin from source. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed James Dumay no ... please first verify (NOT ON DOGFOOD) that you do not see the OPEN link. I closed this because I'm fairly sure you saw this on a broken dogfood and didn't verify on a clean Jenkins. The OPEN link does/should appear on the "Started" toast popup. There are 2 toasts ... the "Queued" one after the queuing request and the "Started" one as soon as the run actually starts. There's no possible link for queued because there's no run yet. In fact most of the time you don't get to see the queued toast because the started toast comes in over it before you get a chance. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed I just checked on dogfood and the OPEN link is there but, for some reason, doesn't open the run. I tried on a local clean BO and it does open it. My guess ... some issue with the REST API url. I'll create a ticket for that. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Ok so that's the problem right there - we don't want a queued toast at all. We want to see the run toast with an open link where you can open the queued item in the run modal. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Imagine this use case: the queue is very long and my run won't be scheduled for another 10 minutes. I kick off my release build, use the toast to open the run while it is queued so I can monitor its progress as it goes from queued to running then 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed James Dumay that's what we had originally and you guys complained that there wasn't immediate feedback to the user acknowledging that they had pressed the run button. So you want to remove the "Queued" toast again and just have the "Started" one? 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-36953) Can't compile Project with Java 8
Title: Message Title BrowserStack Integrations commented on JENKINS-36953 Re: Can't compile Project with Java 8 Ebrahim Moshaya, Nico Po please make the following changes to your pom.xml and try again. Remove the dependency, org.aspectj aspectjrt 1.7.4 Modify the maven plugin configuration as below, com.browserstack automate-maven-plugin 0.7.2-SNAPSHOT 1.8 1.8 1.8 test-compile Adding a configuration with the appropriate Java levels for your project, (I'm assuming 1.8). 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed I think the requirements may have not have been clear (my fault). When the user hits the run button the "Started OPEN" toast should show immediately (on successfully queuing the run). If we click the open link it should show the result details modal - doesn't matter what state it's in (from a users PoV queued is just another status - shouldn't be treated any differently though the backend does). 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed Fair enough. I'm fairly sure the run modal will only work with a run instance, which is not available at this point, so it will require refactoring so that it actually works off the queueId of the run Vs the runId ... I have a feeling it will get messy. 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-36923) Move bcpkix dependency from jenkins-war to bouncycastle-api plugin
Title: Message Title stephenconnolly resolved as Fixed Fixed towards Jenkins core 2.16 Jenkins / JENKINS-36923 Move bcpkix dependency from jenkins-war to bouncycastle-api plugin Change By: stephenconnolly Status: In Progress 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.co
[JIRA] (JENKINS-34496) maven-hpi-plugin injecting test for non hpi packaged projects
Title: Message Title stephenconnolly resolved as Fixed Jenkins / JENKINS-34496 maven-hpi-plugin injecting test for non hpi packaged projects Change By: stephenconnolly Status: In Progress 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed I'd imagine so. I think Ivan Meredith is working in that area at the moment. Michael Neale can you chime in here and clarify if someone is working on making the run modal work off of a queued item? 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-36987) GerritMissedEventsPlaybackManager does not correctly handle multiple gerrit servers
Title: Message Title Francois Ferrand created an issue Jenkins / JENKINS-36987 GerritMissedEventsPlaybackManager does not correctly handle multiple gerrit servers Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Jul/27 8:39 AM Priority: Major Reporter: Francois Ferrand There is a single instance of GerritMissedEventsPlaybackManager, which stores a single status for all Gerrit servers. This causes a few issues: A single timestamp is stored for all servers, instead of storing (and re-loading) each server's timestamp If one server supports event-log and not the other, the isSupported flag is set to false, preventing use of the feature for all servers Add Comment
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY reopened an issue Reopening after talking to James Dumay ... he wants to change how this works so that the run details modal also works with only having a queue item (i.e. without a run) and so we get rid of the "Started" toast. So we need to move the "OPEN" link to the "Queued" toast and zap the "Started" toast completely. That part is trivial. I suspect that the hard part is the refactoring of how the run modal works because it needs to be wired to the redux store in such a way as to accommodate the fact that it started life without a run (or with a "fake" run that only has a queueId and does not have a runId) and then morphs once the run actually becomes available. Sounds tricky, but maybe it's not so bad. Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Issue Type: Bug Improvement 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-36953) Can't compile Project with Java 8
Title: Message Title Nico Po commented on JENKINS-36953 Re: Can't compile Project with Java 8 Just updated pom.xml according to your recommendations. Seems to work fine now. Thanks 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Priority: Blocker Major 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-36424) Run modal to also accommodate queued items (and not just runs)
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run modal to also accommodate queued items (and not just runs) Change By: Tom FENNELLY Summary: Run behaviour does modal to also accommodate queued items (and not work as designed just runs) 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-36424) Run modal to also accommodate queued items (and not just runs)
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run modal to also accommodate queued items (and not just runs) Change By: Tom FENNELLY * NOTE: The description on this JIRA is a bit out of date ... better to read the conversation in the comments.* Maybe we should change the JIRA to reflect the main piece of work that needs to take place here? Already changed the summary to reflect that.* Reproduction steps*# Go to a branch tab# Click the run button of a branch# Toast pops up "queued"*Expected (as per JENKINS-35813)*# Go to a branch tab# Click on the run button of a branch # Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued stateThere is enough [data in the response|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#build-a-pipeline] to open a pipeline result in the queued state. *Additional issue*Also if I click on the run multiple times it will queue multiple times yet I get no feedback.In scope: * Tests to capture this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36821) Add history and windows to vm metrics
Title: Message Title stephenconnolly resolved as Fixed 3.1.2.9 Jenkins / JENKINS-36821 Add history and windows to vm metrics Change By: stephenconnolly Status: In Progress 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-36424) Run modal to also accommodate queued items (and not just runs)
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run modal to also accommodate queued items (and not just runs) Change By: Tom FENNELLY *NOTE: The description on this JIRA is a bit out of date ... better to read the conversation in the comments.* Maybe we should change the JIRA description to reflect the main piece of work that needs to take place here? Already changed the summary to reflect that.*Reproduction steps*# Go to a branch tab# Click the run button of a branch# Toast pops up "queued"*Expected (as per JENKINS-35813)*# Go to a branch tab# Click on the run button of a branch # Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued stateThere is enough [data in the response|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#build-a-pipeline] to open a pipeline result in the queued state. *Additional issue*Also if I click on the run multiple times it will queue multiple times yet I get no feedback.In scope: * Tests to capture this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36978) Javascript duplicated in each individual javascript file
Title: Message Title Tom FENNELLY commented on JENKINS-36978 Re: _javascript_ duplicated in each individual _javascript_ file I wouldn't take that Mic !! 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-36939) Email-ext plugin unable to send jelly template as body of the message
Title: Message Title David van Laatum commented on JENKINS-36939 Re: Email-ext plugin unable to send jelly template as body of the message Are you saying templates are not working for freestyle projects? as I said no matter what you do you wont get them to work in pipeline/workflow jobs 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-26281) Allow users to delete builds even if they are supposed to be kept
Title: Message Title Jakub Cechacek commented on JENKINS-26281 Re: Allow users to delete builds even if they are supposed to be kept Additional PR with further fixes send [1]. If applicable a warning about dependant builds is now displayed when user is prompted to confirm the delete action. However this warning does not prevent the deletion anymore and allows users to proceed by confirming the action. [1] https://github.com/jenkinsci/matrix-project-plugin/pull/39 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-36953) Can't compile Project with Java 8
Title: Message Title BrowserStack Integrations resolved as Fixed Jenkins / JENKINS-36953 Can't compile Project with Java 8 Change By: BrowserStack Integrations Status: Open 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-36953) Can't compile Project with Java 8
Title: Message Title BrowserStack Integrations closed an issue as Fixed Jenkins / JENKINS-36953 Can't compile Project with Java 8 Change By: BrowserStack Integrations Status: Resolved 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-36953) Can't compile Project with Java 8
Title: Message Title BrowserStack Integrations commented on JENKINS-36953 Re: Can't compile Project with Java 8 The plugin doesn't support projects that use Cucumber as a test framework. Since the pom changes fixed the issue for Nico Po marking this as resolved. 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-36955) Webhook does not trigger build
Title: Message Title Aneesh Devasthale closed an issue as Fixed Root folder name should exactly match Github repo name. (case sensitive) Jenkins / JENKINS-36955 Webhook does not trigger build Change By: Aneesh Devasthale Status: Open Closed 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.go
[JIRA] (JENKINS-36846) request to have a contribution guildeline to build email-ext-plugin from source
Title: Message Title pooja shah updated an issue Jenkins / JENKINS-36846 request to have a contribution guildeline to build email-ext-plugin from source Change By: pooja shah Attachment: Screen Shot 2016-07-27 at 4.45.59 pm.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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Boguslaw Klimas assigned an issue to Boguslaw Klimas Jenkins / JENKINS-34876 Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Change By: Boguslaw Klimas Assignee: Andreas Oetken Boguslaw Klimas 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-36947) Failed to write into slave jar cache
Title: Message Title Oliver Gondža started work on JENKINS-36947 Change By: Oliver Gondža 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-36988) no information regarding using influx-db with jenkins pipelines
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-36988 no information regarding using influx-db with jenkins pipelines Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2016/Jul/27 12:18 PM Priority: Critical Reporter: Sorin Sbarnea I don't know if Jenkins Pipelines (Jenkinsfile) are supported yet or not but the main plugin wiki page does not say a thing about them. Jenkins Pipelines are the primary kind of job in Jenkins 2.0 and over 80% of the jobs we run are using them so I am looking for a way to get information about ALL jenkins jobs inside a database, so we can query it later. So, either we have a global option for feeding all builds, which would not require any job configuration or we need a solution for both kind of jobs: old-style ones and pipelines. Add Comment
[JIRA] (JENKINS-36971) Support sub directories checkout
Title: Message Title Rafael Pestano commented on JENKINS-36971 Re: Support sub directories checkout Hi Ebrahim Moshaya, can you test this snapshot: http://maven.jenkins-ci.org:8081/content/repositories/snapshots/org/jenkins-ci/plugins/last-changes/1.0.3-SNAPSHOT/last-changes-1.0.3-20160727.122653-5.hpi It should now support .git dir in workspace sub directories. 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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Or checkout variants could be displayed inline, perhaps, if instance were set to a non-null meta-Step value, preconfigured with a delegate. There are two problems with that: The dropdown to select a delegate would still be displayed, which would be confusing. There is no API to create a default instance of the delegate. Normally a config view for the delegate would be displayed with a null instance, so default values in the form controls would be applied. But there is no way to simultaneously request that the delegate descriptor dropdown be preset to a given value, and avoid defining a specific instance of that descriptor. Possibly both issues could be addressed with an extra API honored by the views of the metastep. The second in isolation would be solved if attrs.default were defined here when used in inline mode. But to solve both would presumably require a separate, optional view, such as config-with-delegate, where a delegateDescriptor would be expected. 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 opt
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title
Jesse Glick edited a comment on JENKINS-29922
Re: Promote delegates of metasteps to top-level functions, deprecate $class
Or {{checkout}} variants _could_ be displayed inline, perhaps, if {{instance}} were set to a non-null meta-{{Step}} value, preconfigured with a delegate. There are two problems with that:* The dropdown to select a delegate would still be displayed, which would be confusing.* There is no API to create a default instance of the delegate. Normally a {{config}} view for the delegate would be displayed with a null {{instance}}, so {{default}} values in the form controls would be applied. But there is no way to simultaneously request that the delegate descriptor dropdown be preset to a given value, _and_ avoid defining a specific instance of that descriptor.Possibly both issues could be addressed with an extra API honored by the views of the metastep. The second in isolation would be solved if {{attrs.default}} were defined [here|https://github.com/jenkinsci/workflow-scm-step-plugin/blob/b36d84aaec9ba4cd3bed2f2e062ead3674de3db8/src/main/resources/org/jenkinsci/plugins/workflow/steps/scm/GenericSCMStep/config.jelly#L28] when used in inline mode. But to solve both would presumably require a separate, optional view, such as the {{config -with-delegate }} , where view to switch modes when a {{delegateDescriptor}} would be expected were defined .
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
[JIRA] (JENKINS-36989) Unnecessary CMake auto-download fails and breaks build after upgrade to jenkins2
Title: Message Title Jörg Ziegler created an issue Jenkins / JENKINS-36989 Unnecessary CMake auto-download fails and breaks build after upgrade to jenkins2 Issue Type: Bug Assignee: Unassigned Components: cmakebuilder-plugin Created: 2016/Jul/27 12:40 PM Environment: Master running on linux (docker, jenkins 2.7.1) Slave running on Windows Server 2012R2 CMake plugin 2.4.3 Priority: Minor Reporter: Jörg Ziegler I did a test upgrade for my server from jenkins 1.651.2 to 2.7.1. The slaves are auto-connecting swarm slaves, their configuration hasn't changed. After upgrading, all cmake build projects fail with the following: ERROR: Install from cmake.org [CMake 3.4.1]: No cmake download known for OS `Windows Server 2012 R2` and arch `amd64`. I believe this shouldn't happen, for the following reasons: the auto-download worked fine with Jenkins 1.6 the slaves in question still have cmake 3.4.1 installed (from previous builds) Windows Server 2012R2 qualifies as Windows OS in https://github.com/jenkinsci/cmakebuilder-plugin/blob/master/src/main/java/hudson/plugins/cmake/CmakeInstaller.java#L373 Any idea what might be going wrong or how to fix this would be appreciated.
[JIRA] (JENKINS-19453) Slave launcher fails after NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Oliver Gondža closed an issue as Fixed Jenkins / JENKINS-19453 Slave launcher fails after NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer Change By: Oliver Gondža Status: Resolved 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-26603) Active Directory trying to connect to AD server every 15 seconds with a user ID
Title: Message Title Jörg Ziegler commented on JENKINS-26603 Re: Active Directory trying to connect to AD server every 15 seconds with a user ID James Nord/Moe Kobeissi: I just stumbled over a similar (the same?) issue. For me the auth burst came from swarm slaves attempting to authenticate themselves. I also faced the issue that neither the slaves nor me as a user could authenticate against AD. To make the problem go away I manually had to change the authentication strategy in config.xml to hudson.security.AuthorizationStrategy$Unsecured Then, after re-entering the password on the security configuration page authentication against AD worked again. This happened after an attempted LTS upgrade from jenkins 1.651.2 to 2.7.1 using plugin version 1.47. Note that before the upgrade the authentication worked fine and so did it once I had re-entered the password. 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-36990) Jenkins API conitnues to make use of "Hudson" namespace
Title: Message Title Smouch Smouch created an issue Jenkins / JENKINS-36990 Jenkins API conitnues to make use of "Hudson" namespace Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/27 1:03 PM Environment: ANY Priority: Minor Reporter: Smouch Smouch Understanding how to use the Jenkins API is made especially complex by the fact that much of the useful functionality is only available within the "Hudson" namespace - or at least this is how the documentation appears to present it. This is just plain dumb. It is totally unclear under what circumstances a developer should look in "Hudson" or in "Jenkins" to find the API of interest. As a (very) experienced software developer I am at a complete loss as to how to script what - to my initial impression - should be a trivial script to discover the "culprits" of a build break. Add Comment
[JIRA] (JENKINS-36991) Unable to load class once the loading was interrupted
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-36991 Unable to load class once the loading was interrupted Issue Type: Bug Assignee: Unassigned Components: remoting Created: 2016/Jul/27 1:03 PM Environment: Jenkins 1.609.3, remoting 2.52 Priority: Major Reporter: Oliver Gondža Jenkins.instance in groovy console yields: noformat java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:191) at Script1.class$(Script1.groovy) at Script1.$get$$class$jenkins$model$Jenkins(Script1.groovy) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) noformat Following happened earlier in slave log: noformat Slave.jar version: 2.52 This is a Unix slave Evacuated stdout Slave successfully connected and online Jul 27, 2016 8:36:57 AM jenkins.model.Jenkins SEVERE: Failed to load Jenkins.class hudson.remoting.RemotingSystemException: java.
[JIRA] (JENKINS-36991) Unable to load class once the loading was interrupted
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-36991
Unable to load class once the loading was interrupted
Change By:
Oliver Gondža
{{Jenkins.instance}} in groovy console yields:{ { noformat} } java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:191) at Script1.class$(Script1.groovy) at Script1.$get$$class$jenkins$model$Jenkins(Script1.groovy) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745){ { noformat} } Following happened earlier in slave log:{ { noformat} } Slave.jar version: 2.52This is a Unix slaveEvacuated stdoutSlave successfully connected and onlineJul 27, 2016 8:36:57 AM jenkins.model.Jenkins SEVERE: Failed to load Jenkins.classhudson.remoting.RemotingSystemException: java.lang.InterruptedException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:266) at com.sun.proxy.$Proxy5.fetch3(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:171) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at com.thoughtworks.xstream.XStream.buildMapper(XStream.java:590) at com.thoughtworks.xstream.XStream.(XStream.java:568) at com.thoughtworks.xstream.XStream.(XStream.java:496) at com.thoughtworks.xstream.XStream.(XStream.java:465) at com.thoughtworks.xstream.XStream.(XStream.java:411) at com.thoughtworks.xstream.XStream.(XStream.java:350) at hudson.util.XStream2.(XStream2.java:88) at jenkins.model.Jenkins.(Jenkins.java:4217) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:191) at Script1.class$(Script1.groovy) at Script1.$get$$class$jenkins$model$Jenkins(Script1.groovy) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:121) a
[JIRA] (JENKINS-36748) Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException
Title: Message Title Jesse Glick commented on JENKINS-36748 Re: Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException I would say this may not have been a defect to begin with. The plugin documentation describes the proper usage of this trigger with Job DSL. The Jenkins GUI will ensure that cron is non-null, but from a scripted client like Job DSL you are expected to define all mandatory fields. If cron is meaningfully optional in this context—some Trigger implementations do not really require it, because they have an empty run, though I think this one does—then Trigger.readResolve should set it to the empty string rather than null. 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-26281) Allow users to delete builds even if they are supposed to be kept
Title: Message Title Jakub Cechacek commented on JENKINS-26281 Re: Allow users to delete builds even if they are supposed to be kept Additional PR to core [1] to hide the delete button when whyKeepLog != null . In such cases the build can't be deleted anyway. [1] https://github.com/jenkinsci/jenkins/pull/2483 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-13768) default parameter values are ignored when triggering parameterized build from groovy post-build script
Title: Message Title Rik de Groot updated an issue Jenkins / JENKINS-13768 default parameter values are ignored when triggering parameterized build from groovy post-build script Change By: Rik de Groot Priority: Major Blocker 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-36992) Config History Plugin does not show history of Deleted slaves in the UI
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-36992 Config History Plugin does not show history of Deleted slaves in the UI Issue Type: New Feature Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/Jul/27 1:19 PM Environment: JobConfigHistory-plugin v2.12 Labels: jobconfighistory Priority: Minor Reporter: Alex Taylor I would like Job Config History Plugin to show the config history of deleted slaves(specifically that they were deleted). It appears the plugin does actually have the config history in the filesystem but it will not display that on the UI. It would be great if we could have a section in the UI of the history of slaves which would show all the deleted slave configs including that they were deleted. Add Comment
[JIRA] (JENKINS-36748) Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException
Title: Message Title Daniel Beck commented on JENKINS-36748 Re: Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException Jesse Glick It's ugly – further investigation showed that the problem is that GhprbTrigger#readResolve doesn't call super.readResolve() – which would prevent the invalid trigger from being created. Still a valid robustness improvement IMO. 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-36971) Support sub directories checkout
Title: Message Title Rafael Pestano started work on JENKINS-36971 Change By: Rafael Pestano 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-36827) Blog for personalisation on Jenkins.io
Title: Message Title Cliff Meyers commented on JENKINS-36827 Re: Blog for personalisation on Jenkins.io I was hoping I might get to it before the end of the week, but if you want it out sooner then by all means go ahead 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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Also it looks like the DSLD/GDSL changes were not made yet. 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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Nor has html.groovy, used for static documentation. 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-36852) Dashboard should use JWT to find the authenticated user
Title: Message Title Cliff Meyers commented on JENKINS-36852 Re: Dashboard should use JWT to find the authenticated user I think we might want to rename this ticket and tweak the description: Dashboard should integrate with JWT to determine authenticated user Must expose a store that can be shared into the blueocean-personalization plugin Need to enhance "fetch" code to append JWT token to HTTP header Must gracefully handle token expiration issues. If the server returns a 401, the UI must gracefully catch the exception, request a new token from the endpoint, and retry the request... otherwise this expiration issue could bleed through the entire code base 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-31939) The top value is better to be chosen by default of to have such option
Title: Message Title Viachaslau Kabak commented on JENKINS-31939 Re: The top value is better to be chosen by default of to have such option thanks) will wait for 0.6.2 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-36960) Change display name of AnyJobRestriction
Title: Message Title Alexandru Somai assigned an issue to Alexandru Somai Jenkins / JENKINS-36960 Change display name of AnyJobRestriction Change By: Alexandru Somai Assignee: Alexandru Somai 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-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title Jesse Glick commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class I also plan to deprecate the archive step when archiveArtifacts is available, though ArtifactArchiver needs a fix to default value handling. 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-36993) Cookie header too long, causing a 413 HTTP error
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-36993 Cookie header too long, causing a 413 HTTP error Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/27 2:02 PM Priority: Critical Reporter: Sorin Sbarnea It seems that Jenkins ends-up using a perverse number and size of cookies which do exceed server size limitations. If cookies are under 8K we are a safe but once you excees this number you start getting failed HTTP requests: Cookie header too long, causing a 413 HTTP error It seems that the problem happens more often in dasboard plugin pages but Request Cookies 7828 JSESSIONID.06076fcc 2u4gi9zl7dwp14iar2a1o0qag N/A N/A N/A 47 JSESSIONID.08a6f8d4 18dtnwfvs9jjnbvw9egdr5htr N/A N/A N/A 47 JSESSIONID.0a44c6cc tmcodqnckndz7cp6ccprippi N/A N/A N/A 46 JSESSIONID.0d10d460 1cypmk06mo4es142gpc2qyyts2 N/A N/A N/A 48 JSESSIONID.19530d7b 52s89da9b0qy15lc3ayyu98m1 N/A N/A N/A 47 JSESSIONID.274f8623 1pwmnhvtomwh26u42wdxa79q3 N/A N/A N/A 47 JSESSIONID.2b3b951a 1sc5pl8s8wvyc1rbxz8yoycbin N/A N/A N/A 48 JSESSIONID.36e4f3d2 17qd4agutapkv15n8lkwcunk2r N/A N/A N/A 48 JSESSIONID.37185837 1qgvitss0hj31rsjwfg9ehc6b N/A N/A N/A 47 JSESSIONID.3cb3b18f 1d0rmwk1qfcs51n5d61qocbg6s N/A N/A N/A 48 JSESSIONID.3e6a110c 63s46d0gft5u11asdx1kzyywn N/A N/A N/A 47 JSESSIONID.4275fe69 iltdedkjjtmt150zuc57tck81 N/A N/A N/A 47 JSESSIONID.43446e0f hgina9tuaowj150h90n0vz6hq N/A N/A N/A 47 JSESSIONID.43859f69 olslwnaacmm91couxqb8huaht N/A N/A N/A 47 JSESSIONID.48b678d5 ymppkv4wdrt4s0z4tgq4grzc N/A N/A N/A 46 JSESSIONID.4a12d5c8 nlye7y9xt9ej15gpmu6awuz9l N/A N/A N/A 47 JSESSIONID.4fea4d8d exhi6xh14y8i1hh304tskep1v N/A N/A N/A 47 JSESSIONID.51725cd5 1smholmd89jplye5sei4l875e N/A N/A N/A 47 JSESSIONID.548ec75e 1jzigt3eis3h71eho4
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky created an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2016/Jul/27 2:02 PM Environment: Linux Jenkins 2.15 Git 2.1.0 Git Client Plugin 1.19.7 Git Parameter Plugin 0.6.1 Priority: Major Reporter: George Sakhnovsky Steps to reproduce: 1. Commit something to a branch and push the change. 2. Open Jenkins, find job, click "build with parameters". Expected result: Branch & Tag select boxes populated with branches and tags. Actual result: Sometimes either the branch or select box will contain the following, instead of the branches or tags: Command "git -c core.askpass=true fetch --tags --progress ssh://g...@stash.typography.com:7999/web/hco-clouddashboard.git +refs/heads/:refs/remotes/origin/ --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://stash.typography.com:7999/web/hco-clouddashboard ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log! Workaround: Reload the "build w/ parameters" page.
[JIRA] (JENKINS-36993) Cookie header too long, causing a 413 HTTP error
Title: Message Title
Sorin Sbarnea updated an issue
Jenkins / JENKINS-36993
Cookie header too long, causing a 413 HTTP error
Change By:
Sorin Sbarnea
It seems that Jenkins ends-up using a perverse number and size of cookies which do exceed server size limitations. If cookies are under 8K we are a safe but once you excees this number you start getting failed HTTP requests: Cookie header too long, causing a 413 HTTP error It seems that the problem happens more often in dasboard plugin pages but{code}Request Cookies 7828 JSESSIONID.06076fcc 2u4gi9zl7dwp14iar2a1o0qag N/A N/A N/A 47 JSESSIONID.08a6f8d4 18dtnwfvs9jjnbvw9egdr5htr N/A N/A N/A 47 JSESSIONID.0a44c6cc tmcodqnckndz7cp6ccprippi N/A N/A N/A 46 JSESSIONID.0d10d460 1cypmk06mo4es142gpc2qyyts2 N/A N/A N/A 48 JSESSIONID.19530d7b 52s89da9b0qy15lc3ayyu98m1 N/A N/A N/A 47 JSESSIONID.274f8623 1pwmnhvtomwh26u42wdxa79q3 N/A N/A N/A 47 JSESSIONID.2b3b951a 1sc5pl8s8wvyc1rbxz8yoycbin N/A N/A N/A 48 JSESSIONID.36e4f3d2 17qd4agutapkv15n8lkwcunk2r N/A N/A N/A 48 JSESSIONID.37185837 1qgvitss0hj31rsjwfg9ehc6b N/A N/A N/A 47 JSESSIONID.3cb3b18f 1d0rmwk1qfcs51n5d61qocbg6s N/A N/A N/A 48 JSESSIONID.3e6a110c 63s46d0gft5u11asdx1kzyywn N/A N/A N/A 47 JSESSIONID.4275fe69 iltdedkjjtmt150zuc57tck81 N/A N/A N/A 47 JSESSIONID.43446e0f hgina9tuaowj150h90n0vz6hq N/A N/A N/A 47 JSESSIONID.43859f69 olslwnaacmm91couxqb8huaht N/A N/A N/A 47 JSESSIONID.48b678d5 ymppkv4wdrt4s0z4tgq4grzc N/A N/A N/A 46 JSESSIONID.4a12d5c8 nlye7y9xt9ej15gpmu6awuz9l N/A N/A N/A 47 JSESSIONID.4fea4d8d exhi6xh14y8i1hh304tskep1v N/A N/A N/A 47 JSESSIONID.51725cd5 1smholmd89jplye5sei4l875e N/A N/A N/A 47 JSESSIONID.548ec75e 1jzigt3eis3h71eho4k8rdaza8 N/A N/A N/A 48 JSESSIONID.5aa178e0 1dxtz2anfhxfs1frvw1ktfggr7 N/A N/A N/A 48 JSESSIONID.6592fe8d eew3gkyj1l8o9cif5o8ln8u3 N/A N/A N/A 46 JSESSIONID.73adce39 1vt6mllmhd56n1l4dc0grtsi7y N/A N/A N/A 48 JSESSIONID.74bd2137 kdkxy4822ddq13s48cmjjw3xi N/A N/A N/A 47 JSESSIONID.7a9b89d9 vmeh4th6gc8m6n9tmi5erbbb N/A N/A N/A 46 JSESSIONID.7c7db147 165vrj6ue6fji17g9btx7o8j1x N/A N/A N/A 48 JSESSIONID.7c917e83 1fkjcyu9c9vx91rd3vair7s8ny N/A N/A N/A 48 JSESSIONID.8331a6ad 2abr2k4abik46f60yj1kfpha N/A N/A N/A 46 JSESSIONID.835c2805 1qetm2u5bjl691jxmji5lznr2k N/A N/A N/A 48 JSESSIONID.8a34e81a v4sb96i1j0q9sws448d4ytte N/A N/A N/A 46 JSESSIONID.97b7d361 1g0iodxktbvgvo8mxpb4kpq9z N/A N/A N/A 47 JSESSIONID.9bd120c0 1myvzhz8a24561w4lefscmszro N/A N/A N/A 48 JSESSIONID.a5766248 18mztnf7xh9ztwn4r2d7kt3x8 N/A N/A N/A 47 JSESSIONID.aa5ddcf7 qeb09ucmu3i91kgw5w5eaidy1 N/A N/A N/A 47 JSESSIONID.abcdc9af 1xi98hmjvlfl21uiwi4oqq339c N/A N/A N/A 48 JSESSIONID.ad3467b6 1jw5p1vfrj6kxkal5usx8j11a N/A N/A N/A 47 JSESSIONID.ad929966 7njjdod9e75z1i85f2dijjfdg N/A N/A N/A 47 JSESSIONID.b02df523 1l866ji69hfbk1xjnseeteatmv N/A N/A N/A 48 JSESSIONID.b2125fe1 eurlzpaxkl01te7hw4c1kguc N/A N/A N/A 46 JSESSIONID.b493f38d 1pmy4hjoe62f3gv2sa0s4drs8 N/A N/A N/A 47 JSESSIONID.b8222741 1lzsi92ylv2q54ux1onb6htmc N/A N/A
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://git@ stash xxx . typography xxx . com xxx : 7999 xxx /web/hco-clouddashboard.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://stash.typography.com:7999/web/hco-clouddashboard ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build w/ parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://g...@xxx.xxx.xxx:xxx/web/ hco my - clouddashboard repo .git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://stash.typography.com:7999/web/hco-clouddashboard ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build w/ parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://g...@xxx.xxx.xxx:xxx/ web xxx /my-repo.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://stash.typography.com:7999/web/hco-clouddashboard ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build w/ parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://g...@xxx.xxx.xxx:xxx/xxx/my-repo.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://stash.typography.com:7999/web/hco-clouddashboard ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build w/ with parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36995) Slave on Mac OS X with unsigned JNLP
Title: Message Title Giacomo Boccardo created an issue Jenkins / JENKINS-36995 Slave on Mac OS X with unsigned JNLP Issue Type: Bug Assignee: Giuseppe Landolfi Components: slave-setup-plugin Created: 2016/Jul/27 2:07 PM Environment: Jenkins 2.7.1 Mac OS X 10.11.6 Java 1.8.0_102 Priority: Critical Reporter: Giacomo Boccardo Every time I try to run a job on a Mac OS X slave, the build gets stuck on "[EnvInject] - Loading node environment variables." and the Java console is Insecure property: (hudson.showWindowsServiceInstallLink, true) specified in unsigned jnlp file will not be set. Jul 27, 2016 12:58:17 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: JNode If I run the slave using java -jar slave.jar -jnlpUrl http://serverUrl/computer/JNode/slave-agent.jnlp -secret xyz it works and the output is
[JIRA] (JENKINS-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://g...@xxx.xxx.xxx:xxx/xxx/my-repo.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh:// stash xxx . typography xxx . com xxx : 7999 xxx / web xxx / hco my - clouddashboard repo ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build with parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36960) Change display name of AnyJobRestriction
Title: Message Title Alexandru Somai started work on JENKINS-36960 Change By: Alexandru Somai 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-36996) The JNLP launchers should not be available when the JNLP port is disabled
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-36996 The JNLP launchers should not be available when the JNLP port is disabled Issue Type: Improvement Assignee: stephenconnolly Components: core Created: 2016/Jul/27 2:35 PM Priority: Minor Reporter: stephenconnolly We are only confusing users if we leave it as an option when we know it won't work Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36995) Slave on Mac OS X with unsigned JNLP
Title: Message Title Giuseppe Landolfi commented on JENKINS-36995 Re: Slave on Mac OS X with unsigned JNLP Ciao Giacomo, as far as I know, the concerned logic is part of the "core" component. Please let me know if you really meant submitting the bug on the slave setup plugin: if not so, I will route to "core" which seems to me a more appropriate place. Thanks 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-36994) Branch and tag select boxes not being populated correctly
Title: Message Title Boguslaw Klimas commented on JENKINS-36994 Re: Branch and tag select boxes not being populated correctly Hi George Sakhnovsky Propebly is the same issue with this [#https://issues.jenkins-ci.org/browse/JENKINS-36833] 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-36994) Branch and tag select boxes not being populated correctly
Title: Message Title Boguslaw Klimas edited a comment on JENKINS-36994 Re: Branch and tag select boxes not being populated correctly Hi [~gsakhnovsky] Propebly Probably is the same issue with this what that [ # JENKINS-36833| https://issues.jenkins-ci.org/browse/JENKINS-36833] This will be fixed in the release 0.6.2 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 Barry O'Neill commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Is there any possibility that this issue will be picked up? We're stuck in the old pipeline world and would love to use the new 2.0 pipeline, but people here are very fond of the visual representation of the parallel jobs that the older pipeline plugins offer. 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-31791) Cannot load job pages due to HistoryWidget hanging
Title: Message Title Kevin Phillips commented on JENKINS-31791 Re: Cannot load job pages due to HistoryWidget hanging Has anyone confirmed whether or not the use of the MultiJob plugin plays a role in this performance problem? Based on a somewhat superficial review of the build records for jobs of this type, it would appear as though that plugin creates custom build records which recursively reference children jobs of the parent. I also suspect that the sub-builds are being loaded when querying the build history of the parent as well, meaning there may be dozens of XML file accesses for each build item for jobs of this type. If my assumptions prove correct, perhaps a related defect should be created to find some way to optimize the MultiJob plugin to avoid these nested queries. 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-36994) Branch and tag select boxes not being populated correctly
Title: Message Title George Sakhnovsky updated an issue Jenkins / JENKINS-36994 Branch and tag select boxes not being populated correctly Change By: George Sakhnovsky Steps to reproduce:1. Commit something to a branch and push the change.2. Open Jenkins, find job, click "build with parameters".Expected result: Branch & Tag select boxes populated with branches and tags.Actual result:Sometimes either the branch or tag select box will contain the following, instead of the branches or tags:Command "git -c core.askpass=true fetch --tags --progress ssh://g...@xxx.xxx.xxx:xxx/xxx/my-repo.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 1: stdout: stderr: remote: Counting objects: 4, done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 4 (delta 2), reused 0 (delta 0) error: Ref refs/remotes/origin/master is at b6c13d7cb555cbbaaa7d35484e50d59d5d4dc9be but expected d5e92cdff22d793bde120875eaf78d62894ec213 From ssh://xxx.xxx.xxx:xxx/xxx/my-repo ! d5e92cd..b6c13d7 master -> origin/master (unable to update local ref) Pleas look to log!Workaround:Reload the "build with parameters" page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34502) Folders should have health metrics based on a single job
Title: Message Title Mike Kobit commented on JENKINS-34502 Re: Folders should have health metrics based on a single job It would also be great if this could be represented as Taking a quick look, it doesn't seem like this would be too difficult to do from a contributor standpoint, but I have no knowledge around all the semantics of writing an extension for Jenkins (serialization, handling input, concurrency issues). Looking through the source code is semi-helpful, but I am still not 100% sure how I would actually write the code for this. Any tips or links to figuring out the right way to contribute 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title John Ament commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage In addition, since the old pipeline doesn't work in Jenkins 2, that blocks upgrades to newer Jenkins releases 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.
