[JIRA] [build-name-setter-plugin] (JENKINS-34221) GitHub repository is missing a tag for the 1.6.0 release
Title: Message Title Marius Gedminas created an issue Jenkins / JENKINS-34221 GitHub repository is missing a tag for the 1.6.0 release Issue Type: Bug Assignee: Lev Mishin Components: build-name-setter-plugin Created: 2016/Apr/14 5:27 AM Priority: Minor Reporter: Marius Gedminas The GitHub repository has tags for all build-name-setter plugin releases up to 1.5.1, but there's no `build-name-setter-1.6.0 tag`. There's a `description-setter` tag that seems to match that release, but is misnamed. Add Comment
[JIRA] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Lev Mishin updated an issue Jenkins / JENKINS-34195 NPE after upgrade to build-name-setter 1.6.0 Change By: Lev Mishin Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Lev Mishin updated an issue Jenkins / JENKINS-34181 NullPointerException in BuildNameSetter.setup Change By: Lev Mishin Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nuget-plugin] (JENKINS-18202) Nuget executable path not saved on Jenkins restart
Title: Message Title Arnaud TAMAILLON resolved as Fixed Fixed in 0.2 Jenkins / JENKINS-18202 Nuget executable path not saved on Jenkins restart Change By: Arnaud TAMAILLON Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nuget-plugin] (JENKINS-18202) Nuget executable path not saved on Jenkins restart
Title: Message Title Arnaud TAMAILLON closed an issue as Fixed Jenkins / JENKINS-18202 Nuget executable path not saved on Jenkins restart Change By: Arnaud TAMAILLON Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Lev Mishin commented on JENKINS-34195 Re: NPE after upgrade to build-name-setter 1.6.0 I'm working on it Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Lev Mishin updated an issue Jenkins / JENKINS-34195 NPE after upgrade to build-name-setter 1.6.0 Change By: Lev Mishin Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cucumber-reports-plugin] (JENKINS-34220) Sorting report by duration column is sorting by string, not time.
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-34220 Sorting report by duration column is sorting by string, not time. Issue Type: Bug Assignee: Damian Szczepanik Attachments: weird-duration-sort.png Components: cucumber-reports-plugin Created: 2016/Apr/14 4:59 AM Environment: Jenkins v1.656, cucumber reports 2.1.0 Priority: Minor Reporter: Nick Sonneveld When sorting test results by duration, it looks like it is a simple string sort instead of sorting by time. See attached screenshot.
[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Lev Mishin commented on JENKINS-34181 Re: NullPointerException in BuildNameSetter.setup I'm working on it and will check the fix today Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Lev Mishin updated an issue Jenkins / JENKINS-34181 NullPointerException in BuildNameSetter.setup Change By: Lev Mishin Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem?If you run the same job again, does it then succeed?Have you configured any other "Additional Behaviours" in the failing job?Does the same problem happen on every job which uses a shallow clone?Can you provide a series of steps which will duplicate the problem?Does the problem resolve itself if you use the earlier git plugin version (for example 2.4.2, don't use 2.4.3, it contains a job definition data loss bug that you don't want in your Jenkins)? Was the source repository involved in any form of cleanup or deletion of commits or content? JENKINS-10571 seems to suggest that the same message may happen when a branch is deleted from the source repository. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem?If you run the same job again, does it then succeed?Have you configured any other "Additional Behaviours" in the failing job?Does the same problem happen on every job which uses a shallow clone?Can you provide a series of steps which will duplicate the problem? Does the problem resolve itself if you use the earlier git plugin version (for example 2.4.2, don't use 2.4.3, it contains a job definition data loss bug that you don't want in your Jenkins)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem? If you run the same job again, does it then succeed? Have you configured any other "Additional Behaviours" in the failing job? Does the same problem happen on every job which uses a shallow clone? Can you provide a series of steps which will duplicate the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-34219) Work with github oauth (plugin)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34219 Work with github oauth (plugin) Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Apr/14 4:07 AM Priority: Major Reporter: Michael Neale Github OAuth plugin provides both identify and login a user, and team based authorization if enabled (ie if you are an admin of a team, you are an admin of a job that belongs to that repo). This may make sense in a github branch source world (either to integrate with, or offer a similar oauth feature so users can quickly sign in with github and have credentials configured). Add Comment
[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title
Mark Eijsermans commented on JENKINS-34181
Re: NullPointerException in BuildNameSetter.setup
Getting this error when useing GIT_COMMIT env var. Eg:
${BUILD_NUMBER}-${GIT_REVISION,length=7}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title
Mark Eijsermans edited a comment on JENKINS-34181
Re: NullPointerException in BuildNameSetter.setup
Getting this error when useing {{GIT_COMMIT}} env var. Eg:{code}${BUILD_NUMBER}-${ GIT_REVISION GIT_COMMIT ,length=7}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Jon Starbird commented on JENKINS-34195 Re: NPE after upgrade to build-name-setter 1.6.0 I hit this same issue with 1.6.0. The above work around given by Peter does work but this type of bug should be a higher priority than minor, I had to save off practically every single job we have, upwards of 50. I can imagine there are even bigger setups out there than ours so Minor just doesn't cover it so I've bumped it up to Major at the very least. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-34195 NPE after upgrade to build-name-setter 1.6.0 Change By: Jon Starbird Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Joshua Spence created an issue Jenkins / JENKINS-34218 Shallow clone broken after JENKINS-24728 Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Apr/14 1:15 AM Environment: git-plugin 2.4.4 Priority: Critical Reporter: Joshua Spence JENKINS-24728 broke our use of shallow clone. Basically, we are getting the following error: ``` > git config remote.origin.url git@REDACTED # timeout=10 Pruning obsolete local branches Fetching upstream changes from git@REDACTED > git --version # timeout=10 using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress git@REDACTED +refs/heads/:refs/remotes/origin/ --prune --depth=1 Checking out Revision 1f2bf20dfc5a408d56181c9db99ac994545f44c3 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1f2bf20dfc5a408d56181c9db99ac994545f44c3 # timeout=10 FATAL: Could not checkout master with start point 1f2bf20dfc5a408d56181c9db99ac994545f44c3 hudson.plugins.git.GitException: Could not checkout master with start point 1f2bf20dfc5a408d56181c9db99ac994545f44c3 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1990) at
[JIRA] [junit-plugin] (JENKINS-34217) add option to disable historical statistics gathering for test results
Title: Message Title Jim Carrothers commented on JENKINS-34217 Re: add option to disable historical statistics gathering for test results Patch available: https://github.com/jenkinsci/junit-plugin/pull/42 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [junit-plugin] (JENKINS-34217) add option to disable historical statistics gathering for test results
Title: Message Title Jim Carrothers created an issue Jenkins / JENKINS-34217 add option to disable historical statistics gathering for test results Issue Type: Improvement Assignee: Unassigned Components: junit-plugin Created: 2016/Apr/14 12:08 AM Priority: Minor Reporter: Jim Carrothers On a Gerrit voter build, where the previous build result could be an entirely different patchset group, or even from an entirely different branch, it likely does not make sense to calculate how many builds a test has been failing for, or to display the test trend chart. I would like a per-job option to disable this work, as doing so would also increase performance for very busy voter builds which keep hundreds or thousands of build records at a time. Add Comment
[JIRA] [s3-plugin] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Joshua Spence created an issue Jenkins / JENKINS-34216 Failed to reset the request input stream Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Apr/14 12:06 AM Environment: s3-plugin 0.9.2 Priority: Major Reporter: Joshua Spence After upgrading the S3 plugin to version 0.9.2 we are seeing S3 uploads fail intermittently. Below is a stack trace (with some details redacted): ``` Publish artifacts to S3 Bucket Using S3 profile: REDACTED Publish artifacts to S3 Bucket bucket=REDACTED, file=9fc530ed8ac7866e6cfcc5132c34614b1e5e6dbd region=us-east-1, upload from slave=false managed=false , server encryption false Publish artifacts to S3 Bucket bucket=REDACTED, file=master region=us-east-1, upload from slave=false managed=false , server encryption false ERROR: Failed to upload files java.io.IOException: Call fails for Destination [bucketName=REDACTED, objectName=REDACTED]: com.amazonaws.ResetException: Failed to reset the request input stream; If the request involves an input stream, the maximum stream buffer size can be configured via request.getRequestClientOptions().setReadLimit(int):: Failed after 1 tries. at hudson.plugins.s3.S3Profile.repeat(S3Profile.java:220) at hudson.plugins.s3.S3Profile.upload(S3Profile.java:145) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:193) at
[JIRA] [core] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [jira-plugin] (JENKINS-13503) Add ability for JIRA plugin to post changelog to a JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-13503 Re: Add ability for JIRA plugin to post changelog to a JIRA Jan, did you have any chance to work on this? Also see the related ticket as this might be quite useful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-plugin] (JENKINS-34215) Disable rate_limit check for GitHub Enterprise
Title: Message Title Ryan Trauntvein created an issue Jenkins / JENKINS-34215 Disable rate_limit check for GitHub Enterprise Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Apr/13 11:11 PM Labels: plugin github-plugin Priority: Minor Reporter: Ryan Trauntvein As GitHub Enterprise does not enforce rate limiting, requests to https://hostname/api/v3/rate_limit will return a 404 Not Found status code. Based on https://github.com/kohsuke/github-api/blob/d30b0403ceb06c71dc9b099352fb9f03045772aa/src/main/java/org/kohsuke/github/GitHub.java#L257 there is a check, and then the rate limit is set to an arbitrary high number. On very busy systems this results in tens of thousands of requests per hour to the GitHub Enterprise appliance. Although returning a 404 is a relatively simple operation, there are other things such as logging that are impacted by the volume of requests. A better method would be to look for /api/v3/ within the API URL, and then simply skip the rate limit check altogether. /api/v3/ is unique to GitHub Enterprise, so this will not have any impact on the GitHub.com rate limit endpoint of https://api.github.com/rate_limit
[JIRA] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-34146 Re: Disabled parametrized jobs could be build from build URL I made a pull request with the change https://github.com/jenkinsci/jenkins/pull/2262 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title Arnaud Héritier commented on JENKINS-34213 Re: Under high throughput the Unexporter can fail to clean up fast enough stephenconnolly why is is it resolved ? The fix isn't yet merged / released ?? https://github.com/jenkinsci/remoting/commit/aee5a6f1756d6bcfba0123567e0195c4d584f8a2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title Ivan Fernandez Calvo updated JENKINS-34146 Jenkins / JENKINS-34146 Disabled parametrized jobs could be build from build URL Change By: Ivan Fernandez Calvo Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-34146 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-34146 Disabled parametrized jobs could be build from build URL Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title
Ivan Fernandez Calvo reopened an issue
I could reproduce it on 1.642.3.2
in ParameterizedJobMixIn ask for parameters before to check if it is asJob().isBuildable()
public final void doBuild(StaplerRequest req, StaplerResponse rsp, @QueryParameter TimeDuration delay) throws IOException, ServletException {
if (delay == null) {
delay = new TimeDuration(asJob().getQuietPeriod());
}
// if a build is parameterized, let that take over
ParametersDefinitionProperty pp = asJob().getProperty(ParametersDefinitionProperty.class);
if (pp != null && !req.getMethod().equals("POST")) {
// show the parameter entry form.
req.getView(pp, "index.jelly").forward(req, rsp);
return;
}
hudson.model.BuildAuthorizationToken.checkPermission(asJob(), asJob().getAuthToken(), req, rsp);
if (pp != null) {
pp._doBuild(req, rsp, delay);
return;
}
if (!asJob().isBuildable()) {
throw HttpResponses.error(SC_INTERNAL_SERVER_ERROR, new IOException(asJob().getFullName() + " is not buildable"));
}
This order solve de problem.
public final void doBuild(StaplerRequest req, StaplerResponse rsp, @QueryParameter TimeDuration delay) throws IOException, ServletException {
if (delay == null) {
delay = new TimeDuration(asJob().getQuietPeriod());
}
if (!asJob().isBuildable()) {
throw HttpResponses.error(SC_INTERNAL_SERVER_ERROR, new IOException(asJob().getFullName() + " is not buildable"));
}
// if a build is parameterized, let that take over
ParametersDefinitionProperty pp = asJob().getProperty(ParametersDefinitionProperty.class);
if (pp != null && !req.getMethod().equals("POST")) {
// show the parameter entry form.
req.getView(pp, "index.jelly").forward(req, rsp);
return;
}
Jenkins / JENKINS-34146
Disabled parametrized jobs could be build from build URL
Change By:
Ivan Fernandez Calvo
Resolution:
Cannot Reproduce
Status:
[JIRA] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title M Chon commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes Wow! Looks much better now! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34209) Pipeline plugin installs in upgrade wizard throws exceptions
Title: Message Title Daniel Beck commented on JENKINS-34209 Re: Pipeline plugin installs in upgrade wizard throws exceptions Mercurial Plugin still depends on SCM API 0.1. These extension points were added in 0.3. So it should be possible setting up a Jenkins 1.651.1 install with Mercurial Plugin, manually downgrade SCM API to 0.2, restart, everything works, upgrade to 2.0 RC, install Pipelines, expect it to explode. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Yes, the beta plugin does not require ssh-agent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34209) Pipeline plugin installs in upgrade wizard throws exceptions
Title: Message Title R. Tyler Croy commented on JENKINS-34209 Re: Pipeline plugin installs in upgrade wizard throws exceptions I'll try to nail down some reproduction steps Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34209) Pipeline plugin installs in upgrade wizard throws exceptions
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-34209 Pipeline plugin installs in upgrade wizard throws exceptions Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nuget-plugin] (JENKINS-18202) Nuget executable path not saved on Jenkins restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18202 Re: Nuget executable path not saved on Jenkins restart Code changed in jenkins User: bgregg Path: src/main/java/com/jenkinsci/nuget/NugetTrigger.java src/main/resources/com/jenkinsci/nuget/NugetTrigger/global.jelly http://jenkins-ci.org/commit/nuget-plugin/5221c4d116f0a93d56ae0719b9fe0f16e0129c54 Log: Fix JENKINS-18202 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multi-branch-project-plugin] (JENKINS-34214) Icon used for multibranch projects should not be same as folder
Title: Message Title martinfr62 created an issue Jenkins / JENKINS-34214 Icon used for multibranch projects should not be same as folder Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Apr/13 8:58 PM Environment: Jenkins 2.0-rc-1 workflow-multibranch 2.1 Priority: Minor Reporter: martinfr62 When viewing build jobs it needs to be clear how/where they were created - the 'appearance' of multibranch parents being 'folders' disguises their true nature. Need a way to visually see that the parent is not a real folder, but rather a multibranch job which itself has the configuration necessary to administer real jobs. Add Comment
[JIRA] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title stephenconnolly updated an issue Jenkins / JENKINS-34213 Under high throughput the Unexporter can fail to clean up fast enough Change By: stephenconnolly Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34213 Re: Under high throughput the Unexporter can fail to clean up fast enough Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/remoting/RemoteInvocationHandler.java http://jenkins-ci.org/commit/remoting/aee5a6f1756d6bcfba0123567e0195c4d584f8a2 Log: [FIXED JENKINS-34213] Ensure that the unexporter cleans up whatever it can each sweep Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title stephenconnolly assigned an issue to stephenconnolly Jenkins / JENKINS-34213 Under high throughput the Unexporter can fail to clean up fast enough Change By: stephenconnolly Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34213 Under high throughput the Unexporter can fail to clean up fast enough Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-34213) Under high throughput the Unexporter can fail to clean up fast enough
Title: Message Title stephenconnolly created an issue Jenkins / JENKINS-34213 Under high throughput the Unexporter can fail to clean up fast enough Issue Type: Bug Assignee: Unassigned Components: remoting Created: 2016/Apr/13 8:51 PM Priority: Minor Reporter: stephenconnolly The Unexporter does not try to drain the queue, rather it unexports at most one object every 200ms... which can create GC pressure when the remoting layer is under stress. Add Comment
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Paul Eipper commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Today I am using SSH Agent Plugin, which works with Git Plugin both for clone and submodule as is. Does this new beta feature removes the need for SSH Agent Plugin in that case? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds Will investigate. IIRC last two paragraphs don't work as described, which is why I changed the behavior to begin with. If it's possible to address that part while restoring the previous quiet period behavior, I'll do so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-33491 Quiet Period does not refresh for subsequent builds Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33491) Quiet Period does not refresh for subsequent builds
Title: Message Title Łukasz Chełmicki commented on JENKINS-33491 Re: Quiet Period does not refresh for subsequent builds In version 1.617 this feature was working fine. I even found the original description of this feature (https://jenkins.io/blog/2010/08/11/quiet-period-feature/) and current implementation changes fundaments of it. You mentioned that polling is resetting this timer, then bug is in implementation of polling mechanism if no changes in repo resets timer (no changes = no trigger = no timer reset) or people are incorrectly setting the quiet period value. Please give us back correct/previous implementation of this feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Jacob Blain Christen commented on JENKINS-34181 Re: NullPointerException in BuildNameSetter.setup When 1.6 was installed, I re-saved the config for one job via the UI and was still encountering the error. Going back and explicitly setting runAtStart to false had it "working" in that if no longer threw the NPE but now the job name isn't updated until the tail end of execution whereas the prior behavior of setting when the envvars became available was more desirable. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-27496) NPE during submission of EnvInject JobProperty when the formis empty
Title: Message Title
Duncan Mak updated an issue
Jenkins / JENKINS-27496
NPE during submission of EnvInject JobProperty when the formis empty
Change By:
Duncan Mak
The issue is a follow-up to the discussion in JENKINS-19852...The issue happens due to the improper fix in https://github.com/jenkinsci/envinject-plugin/commit/f28c26b7c4e346157fcaf2f284582e29457bb1ff* JobProperty::reconfigure(req, form) may return null if the property should be removed* See http://javadoc.jenkins-ci.org/hudson/model/JobProperty.html#reconfigure%28org.kohsuke.stapler.StaplerRequest,%20net.sf.json.JSONObject%29* property.info != null check fails{quote}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at
[JIRA] [build-timeout-plugin] (JENKINS-34115) Quiet period doesn't reset on POST buildWithParameters
Title: Message Title Łukasz Chełmicki commented on JENKINS-34115 Re: Quiet period doesn't reset on POST buildWithParameters Same behavior but with basic auth. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34137) Possible to close install wizard during plugin install.
Title: Message Title Daniel Beck commented on JENKINS-34137 Re: Possible to close install wizard during plugin install. Depending on how this issue would be resolved I'd rather not merge a change that results in people experiencing JENKINS-34174 having absolutely no way out of the dialog (and navigating away does not remove it from the root URL). Unfortunately we have no data to go by how common the problem reported there is, but ecen if it's only a moderate number of users affected, just getting rid of the 'x' seems like a step backwards. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pipeline-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Michael Scharp created an issue Jenkins / JENKINS-34212 Visualization shows stage failed when an exception is caught Issue Type: Bug Assignee: Sergei Egorov Attachments: Screen Shot 2016-04-13 at 2.04.13 PM.png Components: pipeline-view-plugin Created: 2016/Apr/13 8:13 PM Environment: Jenkins 1.654 Ubuntu Linux Priority: Minor Reporter: Michael Scharp I have a stage with a try/catch block. It attempts to copy an artifact from a previous build. If it can't, the step throws an exception which is caught and handled. In the catch block it copies it from a different location (successfully) and my pipeline continues. However, in visualization, the stage is marked as failed. I would expect that regardless of exceptions thrown, if the stage completes successfully it should be green in visualization. This is the error that is thrown/caught:
[JIRA] [core] (JENKINS-34209) Pipeline plugin installs in upgrade wizard throws exceptions
Title: Message Title Daniel Beck commented on JENKINS-34209 Re: Pipeline plugin installs in upgrade wizard throws exceptions FYI Kohsuke Kawaguchi. R. Tyler Croy Something to investigate tomorrow, perhaps? Not trivial to reproduce, likely requires specifically installing an older version of the SCM API plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33683 Re: Hiding ManagementLink is inconsistent with hiding Action Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java http://jenkins-ci.org/commit/jenkins/8fdca297132b953b5572c97480b8017695f92d6d Log: JENKINS-33683 Annotate Function#getActionUrl() as well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33683 Re: Hiding ManagementLink is inconsistent with hiding Action Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/model/ManagementLinkTest.java http://jenkins-ci.org/commit/jenkins/4c02f1db33820733d9500aaa4e5304b30dc0e2ab Log: JENKINS-33683 Do not restrict invisible action to single test Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33683 Re: Hiding ManagementLink is inconsistent with hiding Action Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/Action.java core/src/main/java/hudson/model/ManagementLink.java core/src/main/java/hudson/model/User.java core/src/main/java/hudson/model/View.java core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/ManagementLinkTest.java http://jenkins-ci.org/commit/jenkins/ac566a91e44e3482083355bd5cde3cf65610c4a3 Log: Merge pull request #2146 from olivergondza/hide-management-link [FIXED JENKINS-33683] - Fix Management link hiding Compare: https://github.com/jenkinsci/jenkins/compare/b17e04c9dc05...ac566a91e44e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33683 Re: Hiding ManagementLink is inconsistent with hiding Action Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/Action.java core/src/main/java/hudson/model/ManagementLink.java core/src/main/java/hudson/model/User.java core/src/main/java/hudson/model/View.java core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/ManagementLinkTest.java http://jenkins-ci.org/commit/jenkins/eefafb2b38a5ee5cf51c72a1e9c902ec6f38dc8e Log: [FIXED JENKINS-33683] Clarify Action methods can return null Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33683 Hiding ManagementLink is inconsistent with hiding Action Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33683) Hiding ManagementLink is inconsistent with hiding Action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33683 Re: Hiding ManagementLink is inconsistent with hiding Action Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/model/ManagementLinkTest.java http://jenkins-ci.org/commit/jenkins/e4d7da6053883be13d8b7398d2d2cbcb87aa01f2 Log: JENKINS-33683 Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-pullrequest-builder-plugin] (JENKINS-34211) TTP on PR will only initiate a single job
Title: Message Title Brian Repko created an issue Jenkins / JENKINS-34211 TTP on PR will only initiate a single job Issue Type: Bug Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 2016/Apr/13 7:32 PM Environment: 2 jobs using the bitbucket PR builder on the same repo. Create a PR and add a "test this please" comment. Only one of the jobs will build. Priority: Minor Reporter: Brian Repko TTP (test this please) functionality only works for one job on a given repository. When a PR is created (or updated) all jobs that are configured with the Bitbucket Pull Request Builder will start. This does not happen for TTP comments. In this case, it looks like the first TTP initiates a job and adds a comment to the PR. This comment is enough to stop any subsequent jobs from executing (it thinks that the TTP has been satisfied). It does not seem to be using either the job name or the CI Identifier (which we set to be job name). The Stash Pull Request Builder does handle multiple jobs / TTP properly. also see - https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/issues/82
[JIRA] [core] (JENKINS-34210) Memory leak in Jenkins frontend when updating executors
Title: Message Title
Gustaf Lundh created an issue
Jenkins / JENKINS-34210
Memory leak in Jenkins frontend when updating executors
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Apr/13 7:24 PM
Environment:
Chrome (Ubuntu, Debian), Firefox.
Labels:
jenkins core
Priority:
Major
Reporter:
Gustaf Lundh
In ./war/src/main/webapp/scripts/hudson-behavior.js there is a memory leak triggered by replacing the HTML for the executors panel with fresh content. On installations with a huge list of executors, Chrome can increase in memory usage with over 200MBs every 10minutes by just having the Jenkins dashboard open.
// refresh a part of the HTML specified by the given ID,
// by using the contents fetched from the given URL.
function refreshPart(id,url) {
var f = function() {
if(isPageVisible()) {
new Ajax.Request(url, {
[JIRA] [core] (JENKINS-34174) Jenkins 2.0-rc1 - Getting started hangs installing plugins
Title: Message Title Keith Zantow commented on JENKINS-34174 Re: Jenkins 2.0-rc1 - Getting started hangs installing plugins This definitely looks like some sort of network issue, we can add some timeouts to the plugin downloads, I think, which would end up causing failures to be reported to the installer (which is the right thing to do). This doesn't look like any deadlock issue to me, as these threads are waiting on responses from the OS sockets: "Update center installer thread [#2]: http://updates.jenkins-ci.org/download/plugins/structs/1.1/structs.hpi" Id=80 Group=main RUNNABLE (in native) at java.net.SocketInputStream.socketRead0(Native Method) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34137) Possible to close install wizard during plugin install.
Title: Message Title Keith Zantow commented on JENKINS-34137 Re: Possible to close install wizard during plugin install. Daniel Beck I think we should look at addressing a way of identifying failed installs & providing a means to close the wizard as part of JENKINS-34174 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34209) Pipeline plugin installs in upgrade wizard throws exceptions
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-34209 Pipeline plugin installs in upgrade wizard throws exceptions Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/13 7:13 PM Labels: 2.0 2.0-rc Priority: Critical Reporter: Daniel Beck Reported on IRC: [2016-04-13 07:14:46] rc1 update failed updating Multibranch [2016-04-13 07:14:47] Pipeline: Multibranch [2016-04-13 07:14:47] Failure - [2016-04-13 07:14:47] java.lang.NoClassDefFoundError: jenkins/scm/api/SCMNavigatorDescriptor [2016-04-13 07:14:47] at jenkins.branch.CustomOrganizationFolderDescriptor.doAddSpecificDesc [2016-04-13 07:15:47] it seems to have actually installed fine though, looks normal after restart [2016-04-13 11:08:40] <@danielbeck> benh57_ Still around? If so, could you please explain what exactly was updated, and where you see the error message? [2016-04-13 20:54:23] danielbeck: that error message was on the initial plugin upgrade screen that appears when updating to 2.0rc1. [2016-04-13 20:55:05] <@danielbeck> benh57_ To clarify, are you upgrading or installing new? [2016-04-13 20:55:35] upgrading from 1.6something [2016-04-13 20:55:47] i
[JIRA] [build-pipeline-plugin] (JENKINS-34208) NullPointerException pops up randomly at different steps of a pipeline build
Title: Message Title Gael C. created an issue Jenkins / JENKINS-34208 NullPointerException pops up randomly at different steps of a pipeline build Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Apr/13 7:07 PM Environment: jenkins running on ubuntu, builds are run on docker hosts, based on a pipeline Jenkinsfile, with some concurrency. the NPE does not happen always at the same step, nor at the same task... it seems random. Priority: Major Reporter: Gael C. [INFO] — maven-deploy-plugin:2.7:deploy (default-deploy) @ someSubProject — [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 5.832s [INFO] Finished at: Wed Apr 13 16:53:11 UTC 2016 [INFO] Final Memory: 24M/397M [INFO] [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[JIRA] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes This shouls be fixed now. Update to 1.22 and open issue again if not working! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-34156 git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre edited a comment on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes This shouls should be fixed now. Update to 1.22 and open issue again if not working! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes Code changed in jenkins User: Tomas Bjerre Path: pom.xml http://jenkins-ci.org/commit/git-changelog-plugin/10ebd79f8643079eceab7941244c4af160d5c19c Log: Including correct commits + performance JENKINS-34156 Found major performance problem when sorting tags by commit time, fixed. Now not following parents, unless from is merged into them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-name-setter-plugin] (JENKINS-34195) NPE after upgrade to build-name-setter 1.6.0
Title: Message Title
Peter Rifel commented on JENKINS-34195
Re: NPE after upgrade to build-name-setter 1.6.0
I experienced this too. I noticed that the config.xml for the failing job did not have tags for the new settings in 1.6.0. Simply resaving the job added them to the configuration with their default values and the job began working again.
Before the save (notice the 1.6.0 version)
"build-name-setter@1.6.0">
#${BUILD_NUMBER}
Compared to after the save:
"build-name-setter@1.6.0">
#${BUILD_NUMBER}
true
true
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [openstack-cloud-plugin] (JENKINS-29993) Plugin cannot handle images with no name
Title: Message Title Oliver Gondža resolved as Fixed Fixed: https://github.com/jenkinsci/openstack-cloud-plugin/commit/c87219cd1f11fae5c1a7e0b783fb533a02b9b4d6 https://jenkins.ci.cloudbees.com/job/plugins/job/openstack-cloud-plugin/183/org.jenkins-ci.plugins$openstack-cloud/artifact/org.jenkins-ci.plugins/openstack-cloud/2.3-SNAPSHOT/openstack-cloud-2.3-SNAPSHOT.hpi Jenkins / JENKINS-29993 Plugin cannot handle images with no name Change By: Oliver Gondža Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [openstack-cloud-plugin] (JENKINS-29993) Plugin cannot handle images with no name
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-29993 Plugin cannot handle images with no name Change By: Oliver Gondža Assignee: Marat Mavlyutov Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-workflow-plugin] (JENKINS-34207) Finding the ports exposed by the container
Title: Message Title Adrien Lecharpentier commented on JENKINS-34207 Re: Finding the ports exposed by the container PR: https://github.com/jenkinsci/docker-workflow-plugin/pull/40 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-blocker-plugin] (JENKINS-34206) Build Blocker Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton commented on JENKINS-34206 Re: Build Blocker Plugin stopped letting me decide how to resolve block loops Hmm, I could be wrong about the fix for JENKINS-28926 being the problem - I believe the prior stable version I was running was 1.609.3 (that's what a saved config.xml file that I have claims), and that claims to have the JENKINS-28926 fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-workflow-plugin] (JENKINS-34207) Finding the ports exposed by the container
Title: Message Title
Adrien Lecharpentier created an issue
Jenkins / JENKINS-34207
Finding the ports exposed by the container
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
2016/Apr/13 6:06 PM
Priority:
Minor
Reporter:
Adrien Lecharpentier
I know it's possible to
docker.build("foo/bar:${env.BUILD_ID}").run('-p 4567:80')
so we know that the port 80 is exposed on port 4567. However, when we want to validate the Docker image, we might want to run the image with -P so the {{EXPOSE}}d ports are assigned randomly and so we can have multiple docker container running at the same time.
In the end, we could use
def ip = sh "docker port ${container.id} 8080"
input "http://${ip}. Is it ok?"
but it could be nice to be able to have something like container.port 8080 to do so.
[JIRA] [build-blocker-plugin] (JENKINS-34206) Build Blocker Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton updated an issue Jenkins / JENKINS-34206 Build Blocker Plugin stopped letting me decide how to resolve block loops Change By: David Carlton Summary: Build - Blocker - Plugin stopped letting me decide how to resolve block loops Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-blocker-plugin] (JENKINS-34206) Build-Blocker-Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton commented on JENKINS-34206 Re: Build-Blocker-Plugin stopped letting me decide how to resolve block loops cc stephenconnolly given the commits in JENKINS-27871 / JENKINS-28926 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-blocker-plugin] (JENKINS-34206) Build-Blocker-Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton updated an issue Jenkins / JENKINS-34206 Build-Blocker-Plugin stopped letting me decide how to resolve block loops Change By: David Carlton I recently upgraded Jenkins from 1.609 to 1.642 (using the stable Debian releases); when I did that, Build Blocker Plugin stopped working as expected. (The version of Build Blocker Plugin was 1.7.3 in both cases.) The problem involved two classes of jobs that I have, "Upgrade" jobs and "IT" jobs: I don't want Upgrade jobs to run at the same times as IT jobs or vice-versa, and in the case of a conflict, I want the in-progress IT jobs to finish (without launching any new IT jobs) and then the Upgrade jobs to start.I have this configured with the Build Blocker Plugin: Upgrade jobs block on ITs, but only on running jobs, _not_ on jobs in the queue, whereas IT jobs block on Upgrade jobs, _including_ the jobs in the queue. This gave me the desired behavior with Jenkins 1.609; with 1.642, however, I observed newly launched IT jobs running even when Upgrade jobs were in the queue at the time when I launched those IT jobs . (Though the Upgrade jobs did seem to be blocking properly on running IT jobs.)Looking through the Jenkins Changelog, I was suspicious of JENKINS-28926, which came in with 1.618; I've now downgraded to 1.611 (because I want the fix for JENKINS-27871, which appeared in 1.610), and blocking seems to be working as expected again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups
[JIRA] [build-blocker-plugin] (JENKINS-34206) Build-Blocker-Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton updated an issue Jenkins / JENKINS-34206 Build-Blocker-Plugin stopped letting me decide how to resolve block loops Change By: David Carlton I recently upgraded Jenkins from 1.609 to 1.642 (using the stable Debian releases); when I did that, Build Blocker Plugin stopped working as expected. (The version of Build Blocker Plugin was 1.7.3 in both cases.) The problem involved two classes of jobs that I have, "Upgrade" jobs and "IT" jobs: I don't want Upgrade jobs to run at the same times as IT jobs or vice-versa, and in the case of a conflict, I want the running in-progress IT jobs to finish (without launching any new IT jobs) and then the Upgrade jobs to start.I have this configured with the Build Blocker Plugin: Upgrade jobs block on ITs, but only on running jobs, _not_ on jobs in the queue, whereas IT jobs block on Upgrade jobs, _including_ the jobs in the queue. This gave me the desired behavior with Jenkins 1.609; with 1.642, however, I observed IT jobs running even when Upgrade jobs were in the queue. (Though the Upgrade jobs did seem to be blocking properly on running IT jobs.)Looking through the Jenkins Changelog, I was suspicious of JENKINS-28926, which came in with 1.618; I've now downgraded to 1.611 (because I want the fix for JENKINS-27871, which appeared in 1.610), and blocking seems to be working as expected again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] [build-blocker-plugin] (JENKINS-32903) Build-Blocker-Plugin does not block
Title: Message Title David Carlton commented on JENKINS-32903 Re: Build-Blocker-Plugin does not block I'm seeing a block problem, too - I filed SUMO-34206, because my symptoms are somewhat different, but it wouldn't surprise me if it has the same root cause. (If so, downgrading to a version before 1.618 might work.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-blocker-plugin] (JENKINS-34206) Build-Blocker-Plugin stopped letting me decide how to resolve block loops
Title: Message Title David Carlton created an issue Jenkins / JENKINS-34206 Build-Blocker-Plugin stopped letting me decide how to resolve block loops Issue Type: Bug Assignee: Unassigned Components: build-blocker-plugin Created: 2016/Apr/13 5:53 PM Environment: Jenkins 1.642; Build Blocker Plugin 1.7.3. Priority: Critical Reporter: David Carlton I recently upgraded Jenkins from 1.609 to 1.642 (using the stable Debian releases); when I did that, Build Blocker Plugin stopped working as expected. (The version of Build Blocker Plugin was 1.7.3 in both cases.) The problem involved two classes of jobs that I have, "Upgrade" jobs and "IT" jobs: I don't want Upgrade jobs to run at the same times as IT jobs or vice-versa, and in the case of a conflict, I want the running IT jobs to finish and then the Upgrade jobs to start. I have this configured with the Build Blocker Plugin: Upgrade jobs block on ITs, but only on running jobs, not on jobs in the queue, whereas IT jobs block on Upgrade jobs, including the jobs in the queue. This gave me the desired behavior with Jenkins 1.609; with 1.642, however, I observed IT jobs running even when Upgrade jobs were in the queue. (Though the Upgrade jobs did seem to be blocking properly on running IT jobs.) Looking through
[JIRA] [kubernetes-plugin] (JENKINS-30894) Kubernetes plugin should support certificate-based https API calls
Title: Message Title Carlos Sanchez closed an issue as Fixed PR has been merged Jenkins / JENKINS-30894 Kubernetes plugin should support certificate-based https API calls Change By: Carlos Sanchez Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: R. Tyler Croy Labels: 2.0 workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title Daniel Beck commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message FYI Oleg Nenashev See above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title BBVA updated an issue Jenkins / JENKINS-19445 Jobs randomly stuck with "building remotely on slave-name" message FYI, we have a patch for jenkins/remoting-2.47 that allows to by-pass this issue by defining property hudson.remoting.RemoteClassLoader.force to com.sun.jna.Native. This forces the load of the offending class early on at any UserRequest with a new ClassLoader. We have tested this patch timed job every 5 minutes, with a dormant slave that needs to be waken. We will be requesting merge in github master shortly. Change By: BBVA Attachment: remoting-2.47.patch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [openstack-cloud-plugin] (JENKINS-34100) Launch of cloud slave fails with "No route to host"
Title: Message Title Oliver Gondža commented on JENKINS-34100 Re: Launch of cloud slave fails with "No route to host" Hmm, there ware some changes to the code in 2.1 where I expected to improve the situation. Please have a look into the service log for messages involving the slave name. Also, what is in the $JENKINS_HOME/logs/slaves/$SLAVE_NAME? Usually, there is couple of logs tracking how several instances of "no route to host" / "connection refused" turned into successful connection. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Christopher Shannon commented on JENKINS-34203 Re: Webpage for Git Client Plugin is empty And it's fixed - thanks so much for reporting this in the right place! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Mark Waite edited a comment on JENKINS-34203 Re: Webpage for Git Client Plugin is empty I think the preferred way to receive plugin updates is through the "Update Center" that is part of Jenkins. You can reach it from http://localhost/pluginManager/ (replacing localhost with the hostname and port number of your Jenkins server). If the list has not been refreshed recently, you can refresh the list with the "check now" button.There is a Jenkins infrastructure project which may be a better choice for these types of reports.In the interim, I've sent a request to the mailing list asking for [help undoing the damage|https://groups.google.com/forum/#!topic/jenkinsci-users/KQvx8FNN6j4] which seems to have been done by Steve Cohen. Using a bug report for this type of problem means that there are very few people (1-3) who will see your request. Using the mailing list for this means that there are many more people who may be able to help more effectively. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title KK G commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Today, I tried on windows 10/ windows 7/ windows 2008 too with Jenkins LTS and Jenkins 2.0. None of them works. This basic issue makes Jenkins pipeline unusable on Windows OS. May you please give it a high priority. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Mark Waite commented on JENKINS-34203 Re: Webpage for Git Client Plugin is empty I think the preferred way to receive plugin updates is through the "Update Center" that is part of Jenkins. You can reach it from http://localhost/pluginManager/ (replacing localhost with the hostname and port number of your Jenkins server). If the list has not been refreshed recently, you can refresh the list with the "check now" button. There is a Jenkins infrastructure project which may be a better choice for these types of reports. In the interim, I've sent a request to the mailing list asking for help undoing the damage which seems to have been done by Steve Cohen. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-34203) Webpage for Git Client Plugin is empty
Title: Message Title Christopher Shannon commented on JENKINS-34203 Re: Webpage for Git Client Plugin is empty I understand that it may not fit here, but I'm just an outside user and am letting you know that I cannot download the plugin right now. I would think that would be something important to the developers of the project... I have no idea where this issue should be filed instead. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [violations-plugin] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Pedro Algarvio created an issue Jenkins / JENKINS-34205 Add support for workflow/pipeline to the violations plugin Issue Type: Improvement Assignee: peterkittreilly Components: violations-plugin, workflow-plugin Created: 2016/Apr/13 4:19 PM Priority: Major Reporter: Pedro Algarvio Please add support for the workflow/pipeline plugin. This is a followup on https://issues.jenkins-ci.org/browse/JENKINS-26039 Add Comment
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl: bq. copyArtifacts('source-job') { bq. buildSelector { bq. buildNumber('${PROMOTED_NUMBER}') bq. } bq. }something like this is generated at the top level:{ quote} { ${PROMOTED_NUMBER} {quote } } but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl:copyArtifacts('source-job') {buildSelector { buildNumber('${PROMOTED_NUMBER}')}}something like this is generated at the top level: {{ ${PROMOTED_NUMBER} }} but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl:copyArtifacts('source-job') {buildSelector { buildNumber(' ${ PROMOTED_NUMBER } ')}}something like this is generated at the top level: ${ PROMOTED_NUMBER } but this is what is generated within promotions/actions: {quote} ${ PROMOTED_NUMBER } {quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl: {{ bq. copyArtifacts('source-job') { bq. buildSelector { bq. buildNumber('${PROMOTED_NUMBER}') bq. } bq. } }} something like this is generated at the top level:{quote}${PROMOTED_NUMBER}{quote}but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl:{ quote} { copyArtifacts('source-job') {buildSelector { buildNumber('${PROMOTED_NUMBER}')}} {quote } } something like this is generated at the top level:{quote}${PROMOTED_NUMBER}{quote}but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl:{{ copyArtifacts('source-job') {buildSelector { buildNumber('${PROMOTED_NUMBER}')}} }}something like this is generated at the top level:{quote}${PROMOTED_NUMBER}{quote}but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders updated an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Change By:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.given the following partial dsl:{{ copyArtifacts('source-job') {buildSelector { buildNumber('${PROMOTED_NUMBER}')}} }}something like this is generated at the top level:{quote}${PROMOTED_NUMBER}{quote}but this is what is generated within promotions/actions:{quote}${PROMOTED_NUMBER}{quote}The result is Jenkins will mis-interpret the configuration as 'latest' (I'm guessing b/c it's the default class for the selector).I've tracked it down to hudson.plugins.promoted_builds.integrations.jobdsl.PromotionsExtensionPoint#notifyItemCreated(hudson.model.Item, javaposse.jobdsl.plugin.DslEnvironment, boolean), where the conversion to xml is performed - but I don't know enough to venture a guess as to why it works with standard dsl but not when as a promotion step.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] [promoted-builds-plugin] (JENKINS-34204) CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Title: Message Title
Mike Lueders created an issue
Jenkins / JENKINS-34204
CopyArtifacts build selector broken when using Job DSL + Promoted Builds
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
promoted-builds-plugin
Created:
2016/Apr/13 3:56 PM
Priority:
Minor
Reporter:
Mike Lueders
Description copied from https://github.com/jenkinsci/promoted-builds-plugin/pull/88
The issue is that jenkins ends up interpreting all configuration as 'latest successful build', regardless of how 'buildSelector' is configured. It looks like the resulting config.xml of the copyArtifacts step is incorrect. Specifically, the class of the selector is missing.
given the following partial dsl:
copyArtifacts('source-job') { buildSelector { buildNumber('$
Unknown macro: {PROMOTED_NUMBER}
') } }
something like this is generated at the top level:
$
Unknown macro: {PROMOTED_NUMBER}
