[JIRA] [git-plugin] (JENKINS-28165) git ls-remote fails to connect to repo - status code 128
Ken Keefe commented on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 I'm not using a private key. I want to be able to use the username/password credential option. I tried the suggestions you made on the mailing list and it made no difference. Can you tell me what an exception originating from GitSCM.java on line 735 would be caused by? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [embeddable-build-status-plugin] (JENKINS-25008) Add branch specific badges
Kohsuke Kawaguchi commented on JENKINS-25008 Add branch specific badges The PR in question appears to be rejected. I propose we shift the direction a little bit to make this pluggable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27705) Maven pre-build step is broken with Maven 3.3.1
John Tatum edited a comment on JENKINS-27705 Maven pre-build step is broken with Maven 3.3.1 I agree that the functionality mentioned should probably be moved to the Maven Project Plugin, however, I cannot say what that might involve. After a quick look at the code it appears to me that the biggest concern would be that hudson.model.Project implements ProjectWithMaven, which in turn requires use of the MavenInstallation class. The interface itself is only one method, so the actual change would not be huge. A quick search through Jenkins core did not find anywhere that inferMavenInstallation() was being used, but I have no idea wether or not any plugins would be making use of that(either directly or indirectly). I am fairly new to Jenkins from a development perspective, so it would probably be better to have somebody else handle these changes. I will help if I can though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27705) Maven pre-build step is broken with Maven 3.3.1
John Tatum commented on JENKINS-27705 Maven pre-build step is broken with Maven 3.3.1 I agree that the functionality mentioned should probably be moved to the Maven Project Plugin, however, I cannot say what that might involve. After a quick look at the code it appears to me that the biggest concern would be that hudson.model.Project implements ProjectWithMaven, which in turn requires use of the MavenInstallation class. The interface itself is only one method, so the change itself would not be huge. A quick search through Jenkins core did not find anywhere that inferMavenInstallation() was being used, but I have no idea wether or not any plugins would be making use of that(either directly or indirectly). I am fairly new to Jenkins from a development perspective, so it would probably be better to have somebody else handle these changes. I will help if I can though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Andrew Sumner resolved JENKINS-27826 as Fixed Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test I'm happy with adding the matrix project dependancy Change By: Andrew Sumner (01/May/15 12:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [additional-identities-plugin] (JENKINS-28181) Incompatible with email-ext?
Jonathan Langevin created JENKINS-28181 Incompatible with email-ext? Issue Type: Bug Assignee: Nicolas De Loof Components: additional-identities-plugin Created: 01/May/15 12:07 AM Description: When attempting to use email-ext with additional-identities-plugin installed, I get the following error: Apr 30, 2015 1:58:18 PM WARNING hudson.plugins.emailext.ExtendedEmailPublisher sendMail Could not send email. java.lang.NullPointerException at com.cloudbees.jenkins.plugins.AdditionalIdentityResolver.resolveCanonicalId(AdditionalIdentityResolver.java:42) at hudson.model.User.get(User.java:384) at hudson.plugins.emailext.EmailRecipientUtils.convertRecipientString(EmailRecipientUtils.java:82) at hudson.plugins.emailext.EmailRecipientUtils.addAddressesFromRecipientList(EmailRecipientUtils.java:166) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:618) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:335) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:326) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:234) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.596.2 additional-identities-plugin 1.0 email-ext 2.40 Project: Jenkins Labels: email-ext nullpointer additional-identities-plugin 1.596.2 Priority: Critical Reporter: Jonathan Langevin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-plugin] (JENKINS-26447) Remote shell script should be killed when build is aborted
John Tatum commented on JENKINS-26447 Remote shell script should be killed when build is aborted I think that would be non-trivial given the way this plugin executes commands. This plugin does not use an interactive shell, instead it passes a command to the server and awaits a response indicating a return code. Because of that, it would not be able to interrupt the remote process without passing another command to do so. Even in that instance, you would have to know the PID of the remote command. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [publish-over-ssh-plugin] (JENKINS-18769) SSH Publish Plugin - Unable to use the private key provided in the key path
John Tatum updated JENKINS-18769 SSH Publish Plugin - Unable to use the private key provided in the key path Changed component to publish-over-ssh-plugin. Change By: John Tatum (30/Apr/15 11:56 PM) Component/s: publish-over-ssh-plugin Component/s: ssh-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [publish-over-ssh-plugin] (JENKINS-19811) PublishOverSSHPlugin fails occasionally because jsch exception ( verify: false )
John Tatum commented on JENKINS-19811 PublishOverSSHPlugin fails occasionally because jsch exception ( verify: false ) Eric, note that your pull request is for the SSH Plugin and this issue is for the Publish Over SSH Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-timeout-plugin] (JENKINS-28125) No e-mail is sent if build is aborted
ikedam commented on JENKINS-28125 No e-mail is sent if build is aborted Build-timeout plugin stops a build and sets its result to FAILURE using Jenkins core API. http://javadoc.jenkins-ci.org/hudson/model/Executor.html#interrupt(hudson.model.Result) It can be a problem of maven-plugin that a build result gets ABORTED even when it is interrupted with Executor#interrupt(FAILURE). You may file an issue for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-plugin] (JENKINS-24402) jsch version
John Tatum edited a comment on JENKINS-24402 jsch version Correction, this is not a duplicate, as JENKINS-19811 is for the Publish Over SSH Plugin and this issue is for the SSH Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-plugin] (JENKINS-24402) jsch version
John Tatum reopened JENKINS-24402 jsch version Correction, this is not a duplicate, as JENKINS-19811 is for the Publish Over SSH Plugin and this issue is for the SSH Plugin. Change By: John Tatum (30/Apr/15 10:46 PM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-plugin] (JENKINS-24402) jsch version
John Tatum resolved JENKINS-24402 as Duplicate jsch version Resolving this issue as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-19811. Change By: John Tatum (30/Apr/15 10:42 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [copyartifact-plugin] (JENKINS-28096) Copyartifact doesn't work with Workflow's snippet generator.
ikedam
commented on JENKINS-28096
Copyartifact doesn't work with Workflow's snippet generator.
The latter problem (resulting {{step ) was fixed with https://github.com/jenkinsci/copyartifact-plugin/pull/62.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [plugin-proposals] (JENKINS-28164) Provide creation date of job
Daniel Beck updated JENKINS-28164 Provide creation date of job Can and probably should be done in a plugin rather than core. The necessary extension points exist. Change By: Daniel Beck (30/Apr/15 9:49 PM) Labels: api jenkins job plugin Component/s: plugin-proposals Component/s: core Component/s: jobconfighistory-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28164) Provide creation date of job
davehorner commented on JENKINS-28164 Provide creation date of job Using the /jobConfigHistory/api/json endpoint doesn't always work, sometimes jobs are defined with no jobConfigHistory. It works most of the time, but it would make more sense that the core would keep track of the actual date of creation for a job. So I guess I'm asking for a feature/improvement in the core to track actual creation time without using a plugin. Thanks. --dave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-pipeline-plugin] (JENKINS-28180) Build Pipeline background layout does not extend full width of pipeline
Joshua Shinn created JENKINS-28180 Build Pipeline background layout does not extend full width of pipeline Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 30/Apr/15 9:23 PM Description: Jobs with long names cause the background layer in Build Pipeline to not extend the entire width. To reproduce, create three jobs with names exceeding 30 characters and put them in the same pipeline. Grey background layer will not extend properly to fit the entire pipeline. Project: Jenkins Priority: Minor Reporter: Joshua Shinn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [scm-sync-configuration-plugin] (JENKINS-25434) SCM Sync Configuration Plugin Exception trying to set up initial sync
Peter Laird
commented on JENKINS-25434
SCM Sync Configuration Plugin Exception trying to set up initial sync
I hit this too. I got past it by doing the following:
1. realized command line git was missing on the Jenkins box, so installed it (e.g. yum install git)
2. installed the scm-api Jenkins plugin (I am behind a firewall and have to manually upload each plugin).
3. restarted Jenkins
I am pretty sure it was the first line item that caused this issue, but I included #2 just in case not. Make sure to look at the system logs (Manage Jenkins->System Logs) as I found them to be helpful in diagnosing the root cause. Also, restart Jenkins whenever you want to retest it - it seems to help.
As a pre-flight test, you should be able to do this on your Jenkins box:
1. ssh [your host]
2. sudo su jenkins
(you probably need to update /etc/passwd to give the jenkins user a valid shell before this works)
3. cd
4. mkdir test
5. cd test
6. git clone {the repo URL}
If #6 fails, then you have some work to do before looking deeply at SCM Sync.
@stunney it looks like you confirmed you had git command line installed, so it may not be the same problem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [copyartifact-plugin] (JENKINS-28096) Copyartifact doesn't work with Workflow's snippet generator.
Jesse Glick updated JENKINS-28096 Copyartifact doesn't work with Workflow's snippet generator. Change By: Jesse Glick (30/Apr/15 8:40 PM) Labels: workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
Jesse Glick updated JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList Right, it should follow the defined character. Please bear in mind that CpsScmFlowDefinition is merely a convenience. You can achieve the same effect using a CpsFlowDefinition whose inline script allocates a node, checks out the SCM, uses load to parse it, then continues. (See the tutorial.) Change By: Jesse Glick (30/Apr/15 7:10 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
Jesse Glick updated JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList Change By: Jesse Glick (30/Apr/15 7:08 PM) Labels: perforce workflow workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
A C created JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 30/Apr/15 6:34 PM Description: CpsScmFlowDefinition.create() is hard coded to append the "@script" suffix onto workspace directories (line 94 of CpsScmFlowDefinition.java). This suffix string should at least respect the hudson.slaves.WorkspaceList separator character, or provide some other way to change this suffix string, as the @ symbol is often treated as a special character by various tools. Currently, it is entirely impossible to use the workflow plugin with Perforce due to this bug, as @ is an illegal character in Perforce paths. Trying to run a hello world script using "Groovy CPS DSL from SCM" results in: ERROR: failed to start build java.lang.InterruptedException: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Embedded special characters (*, %%, #, @) not allowed in 'C:\Program Files (x86)\Jenkins\jobs\\workspace@script'. at org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:63) at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:277) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:106) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:181) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Environment: Jenkins 1.6.11 Perforce SCM Project: Jenkins Labels: perforce workspace workflow Priority: Blocker Reporter: A C This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27349) Git SCM-polling uses wrong parameter values for a parametrized branchspec
Nicolas De Loof resolved JENKINS-27349 as Fixed Git SCM-polling uses wrong parameter values for a parametrized branchspec Change By: Nicolas De Loof (30/Apr/15 5:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [repo-plugin] (JENKINS-20309) Repo(Gerrit) is behaving differently than from the command line.
scott julian commented on JENKINS-20309 Repo(Gerrit) is behaving differently than from the command line. I have this exact same issue and I can't find anymore information on this. Has this ever been addressed? Slave node: OSX 10.10.3 repo v1.21 repo-plugin v1.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Jesse Glick created JENKINS-28178 Option to disable sandbox in CpsScmFlowDefinition Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 30/Apr/15 4:33 PM Description: Currently CpsScmFlowDefinition enforces sandbox mode on the grounds that whole-script approval is unrealistic (an administrator would need to approve every SCM revision, and Jenkins cannot automatically approve revisions like it could from GUI changes to a CpsFlowDefinition by an administrator). There should however be an option to simply trust the script as it comes from the SCM. This could be checked by default if Jenkins were unsecured; for a secured Jenkins, the default should remain to use the sandbox, though you could switch to trusted mode with a stern warning in form validation explaining that you are responsible for auditing all changes to that SCM repository, and noting that attackers with SCM access could take over control of Jenkins in ways that might make auditing difficult. (For example, someone with push access to a Git repository could push a script which obtains the API token of a legitimate Jenkins administrator, mails it to the attacker, then deletes the current build record; and finally force-push the attacking script out of existence except via the reflog.) Pending such an option, the workaround is given by the tutorial here: define a CpsFlowDefinition with an approved script that checks out the SCM and uses load to run it. This has the same effect at the price of more awkward configuration. Project: Jenkins Labels: security Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28177) Incorrect revision in commit status notifier when multiple SCMs are used
Abel Hegedus
created JENKINS-28177
Incorrect revision in commit status notifier when multiple SCMs are used
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-plugin
Created:
30/Apr/15 4:14 PM
Description:
When using Multiple SCMs to check out several Git repositories in a single build job, the "revision" of the Build (https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/util/Build.java) will be the revision of the first repository in the list in Multiple SCMs.
However, the Github commit status updater will use the same revision for all repositories (https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java#L102). This will cause failures on all repositories other than the first repository.
Workaround: set "Result on failure" to SUCCESS in the Advanced part of the plugin in the Job Configuration.
Exception:
ERROR: Publisher com.cloudbees.jenkins.GitHubCommitNotifier aborted due to exception
java.io.IOException: {"message":"No commit found for SHA: ","documentation_url":"https://developer.github.com/v3/repos/statuses/"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:440)
at org.kohsuke.github.Requester._to(Requester.java:219)
at org.kohsuke.github.Requester.to(Requester.java:173)
at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:731)
at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:127)
at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:84)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1784)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: java.io.IOException: Server returned HTTP response code: 422 for URL: https://api.github.com/repos//statuses/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at org.kohsuke.github.Requester.parse(Requester.java:396)
at org.kohsuke.github.Requester._to(Requester.java:198)
... 13 more
Project:
Jenkins
Labels:
exception
plugin
github
commit-status
Priority:
Minor
Reporter:
Abel Hegedus
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27705) Maven pre-build step is broken with Maven 3.3.1
Rich DiCroce commented on JENKINS-27705 Maven pre-build step is broken with Maven 3.3.1 Yes, that is the plugin I was referring to. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl resolved JENKINS-28172 as Not A Defect ✔ is replaced by ✔ Change By: Alex Earl (30/Apr/15 3:12 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ Yes, yes I am, I guess the last version let it through, but browsers and email clients happily display without the semicolon as well, so I guess this isn't a bug. Sorry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [warnings-plugin] (JENKINS-28174) Limit a Console Parser to a build step
Florian Reinhard commented on JENKINS-28174 Limit a Console Parser to a build step usecase/example log: i'll need a week or two to reproduce this. redirection: (on windows) i do not know a way to redirect the output of build steps to a file and to the jenkins-console or can this be done by means of on-board jenkins functionality? Having no console output on jenkins is somehow no option since you loose the little progress indicator you have for a 1h build job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26657) File context menu missing when installing Slave under windows with jnlp
Tyler Van Gorder commented on JENKINS-26657 File context menu missing when installing Slave under windows with jnlp Both the master and slaves are running in VMs (VMWare I believe). But we are not hosting anything in a containers (like docker). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28123) Jobs stay queued forever if a node with the label is initially unavailable
Daniel Beck commented on JENKINS-28123 Jobs stay queued forever if a node with the label is initially unavailable Is this a duplicate of JENKINS-6492, or what is the difference? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [rundeck-plugin] (JENKINS-27892) Rundeck - Could not find a job with the identifier
Kevin Defives commented on JENKINS-27892 Rundeck - Could not find a job with the identifier Hello Greg, I don't have more than one job with the same exact name and group but I still have the problem. When I called this URL from my browser : http://rundeck-server/rundeck/api/11/jobs?project=RE7&group=SYSTEM I have this response : ... SCAN_BUNDLES SYSTEM RE7 This job should be used to register a new bundle into Rundeck. NB: only last 20 uploaded bundles are registered on Rundeck. ... As you can see, the job exists and it is not a duplicated job. Can you help me? Thanks in advance. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl commented on JENKINS-28172 ✔ is replaced by ✔ Are you missing the semicolon at the end of the entity? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [matrix-project-plugin] (JENKINS-28176) the bare/basic JOB_NAME is not available in matrix builds
Daniel Beck updated JENKINS-28176 the bare/basic JOB_NAME is not available in matrix builds Change By: Daniel Beck (30/Apr/15 2:57 PM) Component/s: matrix-project-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28165) git ls-remote fails to connect to repo - status code 128
Mark Waite edited a comment on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 Does your private key require a passphrase? If so, then you need to generate a private key which does not require a passphrase and use that instead. Alternately, if you really mean a username and a password (rather than a private key), then refer to my e-mail response on the Jenkins mailing list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ I'm not seeing it at all in 2.40 that was auto updated from within Jenkins Plugin manager. :/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28176) the bare/basic JOB_NAME is not available in matrix builds
Florian Reinhard created JENKINS-28176 the bare/basic JOB_NAME is not available in matrix builds Issue Type: Improvement Assignee: Unassigned Components: core Created: 30/Apr/15 2:45 PM Description: Consider a job named "foo". If you have no matrix build JOB_NAME will contain foo If you have a matrix build with Axis1 and Axis2 JOB_NAME will contain foo/Axis1=Value1,Axis2=Value2. At the moment there's no environment variable that contains the bare job name foo. Project: Jenkins Priority: Minor Reporter: Florian Reinhard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl commented on JENKINS-28172 ✔ is replaced by ✔ According to http://www.danshort.com/HTMLentities/?w=dingb, ✔ is a "heavy checkmark." When I put that into the content field and set the content type to HTML, I get the "heavy checkmark" in my email. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ The previous plugin output a tick (symbol). 2.40 just outputs ✔ as text because the ampersand now converts & to the html ampersand token. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ldap-plugin] (JENKINS-28162) Users cannot view the groups they are members of from the user page in jenkins
Daniel Beck commented on JENKINS-28162 Users cannot view the groups they are members of from the user page in jenkins Asked for rationale for the current behavior in https://github.com/jenkinsci/jenkins/pull/577 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ldap-plugin] (JENKINS-28162) Users cannot view the groups they are members of from the user page in jenkins
Daniel Beck resolved JENKINS-28162 as Not A Defect Users cannot view the groups they are members of from the user page in jenkins Not a bug in LDAP plugin, getting a user's authorities (groups) requires Administer permission. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/User.java#L879 File an improvement again core if this needs to be changed. Change By: Daniel Beck (30/Apr/15 2:25 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [warnings-plugin] (JENKINS-28174) Limit a Console Parser to a build step
Ulli Hafner commented on JENKINS-28174 Limit a Console Parser to a build step Maybe it would be easier to improve the regexp in each parser. Can you please show an example log message that is picked by two parsers? (BTW: you can redirect the output to a file to get the desired result) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl commented on JENKINS-28172 ✔ is replaced by ✔ Does your output actually output the entity like that, or is it the original symbol? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Antoine Musso created JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked Issue Type: Bug Assignee: kutzi Components: ircbot-plugin Created: 30/Apr/15 2:10 PM Description: We have recently upgraded the IRC plugin from 2.25 to 2.26. On configuration change, the ircbot plugin invokes PircBotX.shutdown(). For some reason it never finish and the conf change is stalled. A side effect is that jobs sending notifications ends up being blocked waiting for an instance of the irc connection provider. The only fix is to restart Jenkins entirely. Our bug has a few more explanations https://phabricator.wikimedia.org/T96183 and a full thread dump attached https://phabricator.wikimedia.org/P584 Here are the blocked threads: Two jobs are blocked: "Executor #2 for integration-slave-trusty-1016 : executing browsertests-CentralNotice-en.wikipedia.beta.wmflabs.org-windows_7-internet_explorer-10-sauce #234" prio=5 BLOCKED "Executor #1 for integration-slave-trusty-1012 : executing browsertests-PdfHandler-test2.wikipedia.org-linux-firefox-sauce #494" prio=5 BLOCKED hudson.plugins.ircbot.v2.IRCConnectionProvider.getInstance(IRCConnectionProvider.java:14) hudson.plugins.ircbot.IrcPublisher.getIMConnection(IrcPublisher.java:102) hudson.plugins.im.IMPublisher.sendNotification(IMPublisher.java:374) hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:585) hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304) hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291) ... A configuration submit change is blocked as well: "Handling POST /ci/configSubmit from X.X.X.X : RequestHandlerThread[#1683]" daemon prio=5 WAITING sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236) org.pircbotx.Channel.getMode(Channel.java:127) org.pircbotx.Channel.getModeArgument(Channel.java:182) org.pircbotx.Channel.getChannelKey(Channel.java:239) org.pircbotx.PircBotX.shutdown(PircBotX.java:2872) hudson.plugins.ircbot.v2.IRCConnection.close(IRCConnection.java:102) hudson.plugins.im.IMConnectionProvider.releaseConnection(IMConnectionProvider.java:92) hudson.plugins.ircbot.v2.IRCConnectionProvider.setDesc(IRCConnectionProvider.java:19) hudson.plugins.ircbot.IrcPublisher$DescriptorImpl.configure(IrcPublisher.java:336) jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2915) jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2878) ... Some other related threads: "JenkinsIsBusyListener-thread" daemon prio=5 BLOCKED hudson.plugins.im.IMConnectionProvider.currentConnection(IMConnectionProvider.java:83) hudson.plugins.im.JenkinsIsBusyListener.setStatus(JenkinsIsBusyListener.java:118) hudson.plugins.im.JenkinsIsBusyListener.updateIMStatus(JenkinsIsBusyListener.java:109) hudson.plugins.im.JenkinsIsBusyListener.access$000(JenkinsIsBusyListener.java:20) hudson.plugins.im.JenkinsIsBusyListener$3.run(JenkinsIsBusyListener.java:98) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) java.util.concurrent.FutureTask.run(FutureTask.java:262) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) "IM-Reconnector-Thread" daemon prio=5 BLOCKED hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvi
[JIRA] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ 1) Create a new Jenkins job that does nothing. 2) Make sure you have 'Editable Email Notification' as a Post-build Action. 3) Put ✔ into the Default Content box. 4) Make sure you have a valid email address in Project Recipient List. 5) Make sure Content Type is set to HTML (text/html). 6) Hit build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ldap-plugin] (JENKINS-28162) Users cannot view the groups they are members of from the user page in jenkins
Dan Dumont commented on JENKINS-28162 Users cannot view the groups they are members of from the user page in jenkins That link appears to show what I would expect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [warnings-plugin] (JENKINS-28174) Limit a Console Parser to a build step
Florian Reinhard created JENKINS-28174 Limit a Console Parser to a build step Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 30/Apr/15 1:56 PM Description: Imagine a regular build job where you run several build-steps in a row, e.G cmake make (whatever compiler) lint doxygen etc.. Now it sometimes happens that two parsers match the same line and you end up with false positives. So it would be handy to limit a console parser to a specific build step (or may be several build steps, or the otherway round, exclude build-steps). Project: Jenkins Priority: Minor Reporter: Florian Reinhard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl edited a comment on JENKINS-28172 ✔ is replaced by ✔ ✔ Can you provide some text for me to reproduce and test with? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Alex Earl commented on JENKINS-28172 ✔ is replaced by ✔ ```✔``` Can you provide some text for me to reproduce and test with? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [artifactory-plugin] (JENKINS-28173) Add support for empty "Git release branch name prefix"
Bob Tiernay created JENKINS-28173 Add support for empty "Git release branch name prefix" Issue Type: Improvement Assignee: yossis Components: artifactory-plugin Created: 30/Apr/15 1:45 PM Description: Some environments use the Maven pom version as the tag version in git. Currently there is no way to prevent a prefix from being added when performing a release to artifactory. This means that a user must manually strip the prefix from multiple locations in the release form which is error prone. It would be nice to have an checkbox that says "No prefix" to prevent the default prefix from being assigned when the form text fields are left empty. Project: Jenkins Labels: plugin Priority: Minor Reporter: Bob Tiernay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [artifactory-plugin] (JENKINS-28173) Add support for empty "Git release branch name prefix"
Bob Tiernay updated JENKINS-28173 Add support for empty "Git release branch name prefix" Change By: Bob Tiernay (30/Apr/15 1:46 PM) Description: Some environments use the Maven pom version as the tag version in git. Currently there is no way to prevent a default prefix from being added when performing a release to artifactory. This means that a user must manually strip the prefix from multiple locations in the release form which is error prone. It would be nice to have an checkbox that says a "No prefix" to prevent checkbox that prevents the default prefix from being assigned when the form text fields are left empty. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ I give up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ The second ✔ should be & #x214 without the space. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San commented on JENKINS-28172 ✔ is replaced by ✔ The second ✔ should be ✔, steps to reproduce is just put that code into the email to send in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28165) git ls-remote fails to connect to repo - status code 128
Mark Waite commented on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 Does your private key require a passphrase? If so, then you need to generate a private key which does not require a passphrase and use that instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-28172) ✔ is replaced by ✔
Nik San created JENKINS-28172 ✔ is replaced by ✔ Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 30/Apr/15 1:33 PM Description: Email with ✔ are encoded as ✔ which out puts the string literal rather than a tick. Environment: Jenkins 1.608, email-ext 2.40 Project: Jenkins Labels: email-ext Priority: Minor Reporter: Nik San This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
paul ecc commented on JENKINS-23929 Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace For future reference, I was able to get around this bug simply by clearing the "Directory" field, then unchecking "Use custom workspace" then saving. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-27392) API to decorate console output
SCM/JIRA link daemon commented on JENKINS-27392 API to decorate console output Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStep.java pom.xml http://jenkins-ci.org/commit/workflow-plugin/874c4618f43316e096562499f0f6a3636951919a Log: JENKINS-27392 Using SimpleBuildWrapper.createLoggerDecorator from CoreWrapperStep. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-27392) API to decorate console output
SCM/JIRA link daemon commented on JENKINS-27392 API to decorate console output Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java http://jenkins-ci.org/commit/workflow-plugin/4ad6605229b6f248fa06c8d9be9bd8bcdb547f80 Log: JENKINS-27392 Prepared test for SimpleBuildWrapper.createLoggerDecorator. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22941) Way to mark an Executable that should not block isReadyToRestart
SCM/JIRA link daemon commented on JENKINS-22941 Way to mark an Executable that should not block isReadyToRestart Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/285b4501470f321086bcca4f98c871f2d5b6d418 Log: JENKINS-22941 AsynchronousExecution.blocksRestart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25938) Lock an Executor without creating a Thread
SCM/JIRA link daemon commented on JENKINS-25938 Lock an Executor without creating a Thread Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/ee2ca390e73004b411e133c1832b88e977b47f28 Log: JENKINS-25938 Starting to use AsynchronousExecutable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26090) Executables.getExecutor
SCM/JIRA link daemon commented on JENKINS-26090 Executables.getExecutor Code changed in jenkins User: Jesse Glick Path: pom.xml support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/ExecutorPickle.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/5cef1a70d27d1af7015beec6d2ef9c5d8fc8b27a Log: JENKINS-26090 Using Executables.getExecutor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-26128) Dynamically-scoped env step
SCM/JIRA link daemon commented on JENKINS-26128 Dynamically-scoped env step Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStep.java http://jenkins-ci.org/commit/workflow-plugin/932adc8fd4a0c3b73cce54a657da2b7e7f985db1 Log: JENKINS-26128 Demonstrating that non-block-scoped env sets are shadowed by block context. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
SCM/JIRA link daemon commented on JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/2a1899d571c953a87b5b8ced945ef676f9728d69 Log: JENKINS-26900 AsynchronousExecution.displayCell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [workflow-plugin] (JENKINS-26552) @StepContextParameter EnvVars missing Computer.environment
SCM/JIRA link daemon commented on JENKINS-26552 @StepContextParameter EnvVars missing Computer.environment Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java http://jenkins-ci.org/commit/workflow-plugin/74b51c42dba52952b84b73b978cb562a1bb63ad5 Log: Adding some tests. Fails without a fix of JENKINS-26552. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step
Damien Coraboeuf started work on JENKINS-28171 Missing lookupStrategy configuration for the DSL step Change By: Damien Coraboeuf (30/Apr/15 1:00 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step
Damien Coraboeuf commented on JENKINS-28171 Missing lookupStrategy configuration for the DSL step Pull request created at https://github.com/jenkinsci/job-dsl-plugin/pull/465 Current workaround is to not use the dsl block, but to configure it using the configure block. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-28171) Missing lookupStrategy configuration for the DSL step
Damien Coraboeuf created JENKINS-28171 Missing lookupStrategy configuration for the DSL step Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 30/Apr/15 12:37 PM Description: Hi, In the version 1.32, there is no way to configure the lookupStrategy property using the dsl closures. Is that foreseen to add? Thanks, Damien. Environment: job-dsl 1.32 Project: Jenkins Priority: Major Reporter: Damien Coraboeuf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [perforce-plugin] (JENKINS-28142) p4 clean
Rob Petti commented on JENKINS-28142 p4 clean Reverting changed files will perform no better than a full wipe and sync. Ideally, you should not be altering files tracked by perforce in the first place, as that is incredibly bad practice. As for the performance differences, I honestly have no idea. This plugin is more or less unmaintained, so if this is an issue then I recommend wither switching to the new plugin, or just calling p4 clean as a build step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [swarm-plugin] (JENKINS-28148) Fail to create a swarm when using a toolLocations with whitespaces.
Paul Popineau commented on JENKINS-28148 Fail to create a swarm when using a toolLocations with whitespaces. I have posted this PR#28. I would be glad to have insights on it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [script-security-plugin] (JENKINS-28170) Named parameters are not supported in the sandbox
Tom FENNELLY created JENKINS-28170 Named parameters are not supported in the sandbox Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 30/Apr/15 12:01 PM Description: Using a DSL in a workflow script that has a method with named params e.g. Object inside(String link = null, Closure body) Calling it in the workflow (with sandbox mode turned ON) results in the following exception: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (DSL inside java.util.LinkedHashMap com.cloudbees.groovy.cps.impl.CpsClosure) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:155) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:77) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:60) Quote from Jesse: Not sure offhand how to fix; part of the general “Groovy hell” that is SandboxInterceptor: we get a high-level representation of a call point, and have to duplicate an incredibly complex system in Groovy to translate that to an actual Java method call. Project: Jenkins Priority: Major Reporter: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jabber-plugin] (JENKINS-28169) Jabber plugin fails to establish legacy SSL connection, when the Jabber server does not respond on plain communication
Florian Wiesner created JENKINS-28169 Jabber plugin fails to establish legacy SSL connection, when the Jabber server does not respond on plain communication Issue Type: Bug Assignee: kutzi Attachments: jabber-plugin-stacktrace.txt Components: jabber-plugin Created: 30/Apr/15 11:10 AM Description: We're migrating to Jenkins from Hudson. On Hudson we ran with version 22 of the Jabber plugin. Now, with the migration to Jenkins, we cannot connect to our corporate Jabber server anymore that requires legacy SSL enabled. With a plain connection, our Jabber server is not responding at all. Thus smack throws a org.jivesoftware.smack.SmackException$NoResponseException. As the exception handler in hudson.plugins.jabber.im.transport.JabberIMConnection.createConnection doesn't set retryWithLegacySSL to true, there won't be an attempt to connect via legacy SSL, leading to a complete failure of the plugin for us. Environment: Jenkins 1.611, instant-messaging plugin 1.34, japper-plugin 1.34 Project: Jenkins Labels: plugins jabber Priority: Major Reporter: Florian Wiesner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Roy Miller commented on JENKINS-28055 Pipeline arrows are not displaying or displayed incorrectly I'm seeing the same behavior with 1.611. Symptoms include the arrows not displaying correctly, but also very long delay in loading the view. That's probably because of the large number of JS errors related to jquery.isPlumb: Error: Invalid value for attribute width="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713 jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for attribute height="NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713 jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for attribute d="M 53,51 L 78 51 L 77 51 M 78 51 L 78 NaN L 78 NaN M 78 NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN NaN L NaN NaN M NaN NaN L NaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1f @ jquery.jsPlumb-1.3.16-all-min.js:1_paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713 jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for attribute d="MNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN LNaN,NaN"g @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1draw @ jquery.jsPlumb-1.3.16-all-min.js:1paint @ jquery.jsPlumb-1.3.16-all-min.js:1redraw @ jquery.jsPlumb-1.3.16-all-min.js:1be @ jquery.jsPlumb-1.3.16-all-min.js:1bx @ jquery.jsPlumb-1.3.16-all-min.js:1connect @ jquery.jsPlumb-1.3.16-all-min.js:1(anonymous function) @ pipe.js:204jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:200jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:198jQuery.extend.each @ jquery.full.js:384(anonymous function) @ pipe.js:196jQuery.extend.each @ jquery.full.js:384refreshPipelines @ pipe.js:195Q.ajax.success @ pipe.js:9fire @ jquery.full.js:3143self.fireWith @ jquery.full.js:3255done @ jquery.full.js:9309callback @ jquery.full.js:9713 jquery.jsPlumb-1.3.16-all-min.js:1 Error: Invalid value for attribute width="NaN" ... Prioritization is up to you guys, of course, but I don't think this is a Minor priority thing. If it were just display, I could understand. But we've also seen that loading the view pegs the CPU on our build box. That's more of an issue, I believe. This message is automatically generated by JIRA.
[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Yes, the job ran (sauce connect worked although job failed due to a test) and produced those 4.3.8 folders: (...) -rw-r--r-- 1 tomcat tomcat 3596050 Apr 30 12:17 sc-4.3-linux.tar.gz drwxr-xr-x 5 tomcat tomcat4096 Apr 30 12:17 sc-4.3.8-linux (...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I will. Currently some other job is running, so I'm waiting for it to run again. But the thing above is not new - I also mentioned it in case description. So you didn't introduce it now. If it behaves as in the past the /usr/share/tomcat7/sc-4.3.8-linux will appear when next sauce-using job runs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory-plugin] (JENKINS-28158) if JENKINS_URL is set to an https adress, then login over an alternate http address not working
Jens Großmann commented on JENKINS-28158 if JENKINS_URL is set to an https adress, then login over an alternate http address not working If i set: as JENKINS_URL https://ourjenkins.internal then login over https://ourjenkinscustomerdomain.com works login over http://ourjenkinscustomerdomain.com not testable, because automated redirect to https! login over http://ourjenkins.internal not work login over https://ourjenkins.internal not testable, because no ssl configuration on jenkins. SSL termination only from external on loadbalancer/reverse proxy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger-plugin] (JENKINS-28168) gerrit-trigger used cpu 100%
denger tung updated JENKINS-28168 gerrit-trigger used cpu 100% Change By: denger tung (30/Apr/15 9:41 AM) Description: jenkins java proccess used cpu 100%(cpuinfo.png), so i run "ps mp 21008 -o THREAD,tid" show threads(ps-mp-threads.png), i found two threads cpu used highest(jstack-tow-thread.png). It looks deadlocks. ~ and the gerrit trigger can't connect the gerrit server.I can only be resolved by restarted jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Okay, I'm not sure why this error is occuring, as I didn't change the code which launches Sauce Connect in this version. The code should be attempting to extract the .tar.gz file from the Sauce plugin, and expand the contents into the /usr/share/tomcat7/sc-4.3.8-linux directory. After removing the files in the directory, can you clarify whether the /usr/share/tomcat7/sc-4.3.8-linux directory exists? You can also specify a different working directory for Sauce Connect via the 'Manage Jenkins' - 'Configure System' page This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ldap-plugin] (JENKINS-28162) Users cannot view the groups they are members of from the user page in jenkins
Daniel Beck commented on JENKINS-28162 Users cannot view the groups they are members of from the user page in jenkins What about the /whoAmI URL? Are group memberships shown there? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory-plugin] (JENKINS-28158) if JENKINS_URL is set to an https adress, then login over an alternate http address not working
Daniel Beck commented on JENKINS-28158 if JENKINS_URL is set to an https adress, then login over an alternate http address not working I was asking about https://ourjenkins.internal and http://ourjenkinscustomerdomain.com – i.e. what happens when you change only one of (scheme, host). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-28164) Provide creation date of job
Daniel Beck commented on JENKINS-28164 Provide creation date of job Is this issue resolved, or are you still asking for this feature? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26855) Unreachable objects "remoting.Channel" can not garbage collect
denger tung updated JENKINS-26855 Unreachable objects "remoting.Channel" can not garbage collect Change By: denger tung (30/Apr/15 9:22 AM) Description: My jenkins server old generationis 20GB, use than 90%, It should trigger full gc, but seems like it didn't. memory does not decrease so i dump the heap, found 10GB+ "remoting.Channel" unreachable objects in heap. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27216) "remoting.Channel" can not garbage collect
denger tung commented on JENKINS-27216 "remoting.Channel" can not garbage collect slave used JNLP. more details: https://issues.jenkins-ci.org/browse/JENKINS-26855 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27289) Masking classLoader doesn`t work on remote Slave
lior hasson commented on JENKINS-27289 Masking classLoader doesn`t work on remote Slave Hey, Any ETA about this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger-plugin] (JENKINS-28168) gerrit-trigger used cpu 100%
denger tung created JENKINS-28168 gerrit-trigger used cpu 100% Issue Type: Bug Assignee: rsandell Attachments: cpuinfo.png, jstack-tow-thread.png, ps-mp-threads.png Components: gerrit-trigger-plugin Created: 30/Apr/15 9:09 AM Description: jenkins java proccess used cpu 100%(cpuinfo.png), so i run "ps mp 21008 -o THREAD,tid" show threads(ps-mp-threads.png), i found two threads highest(jstack-tow-thread.png). It looks deadlocks. ~ and the gerrit trigger can't connect the gerrit server. I can only be resolved by restarted jenkins. Environment: Linux Jenkins ver. 1.580.1 OS Version: :core-3.0-amd64:core-3.0-ia32:core-3.0-noarch:graphics-3.0-amd64:graphics-3.0-ia32:graphics-3.0-noarch Description: CentOS release 4.3 (Final) Gerrit Trigger Plugin: 2.12.0 JDK: open-jdk 1.7.0 build 24.60-b09, Project: Jenkins Priority: Blocker Reporter: denger tung This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [active-directory-plugin] (JENKINS-28158) if JENKINS_URL is set to an https adress, then login over an alternate http address not working
Jens Großmann commented on JENKINS-28158 if JENKINS_URL is set to an https adress, then login over an alternate http address not working i try it:-/: if JENKINS_URL=https://ourjenkinscustomerdomain.com then login over https://ourjenkinscustomerdomain.com works login over http://ourjenkins.internal not work if JENKINS_URL=http://ourjenkinscustomerdomain.com then login over https://ourjenkinscustomerdomain.com works login over http://ourjenkins.internal works so if is set https as jenkins_url, then the login over an non http url will not work. if set an http url as jenkins url, then the logins over any http or https url will work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 That folder contains only: (...) -rw-r--r-- 1 tomcat tomcat 3587099 Apr 30 10:54 sc-4.3-linux.tar.gz drwxr-xr-x 5 tomcat tomcat4096 Dec 19 17:13 sc-4.3.6-linux (...) I will delete those manually - as I noticed that the plugin will then generate the sc-4.3.8-linux it needs. Will you please fix this problem as well? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I updated to 1.128. I get this error now: Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-10-197-79-50 FATAL: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:358) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286) ... 8 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:135) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) ... 9 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-28167) job-dsl-plugin fails to work on Jenkins ver. 1.557
Karel Striegel
updated JENKINS-28167
job-dsl-plugin fails to work on Jenkins ver. 1.557
Change By:
Karel Striegel
(30/Apr/15 8:53 AM)
Description:
Plugin install + restarted -> no issues.Following the tutorial : https://github.com/jenkinsci/job-dsl-plugin/wiki/Tutorial---Using-the-Jenkins-Job-DSLAfter coying the DSL exmaple Script block, and pressing save. I get the following error msg :{
code}
Stack tracejavax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class javaposse.jobdsl.plugin.ExecuteDslScripts from {"scriptLocation":"true","scriptText":"job('DSL-Tutorial-1-Test') {\nscm {\ngit('git://github.com/jgritman/aws-sdk-test.git')\n}\ntriggers {\nscm('*/15 * * * *')\n}\nsteps {\nmaven('-e clean test')\n}\n}","targets":"","ignoreExisting":false,"removedJobAction":"","removedViewAction":"","lookupStrategy":"JENKINS_ROOT","additionalClasspath":"","stapler-class":"javaposse.jobdsl.plugin.ExecuteDslScripts","kind":"javaposse.jobdsl.plugin.ExecuteDslScripts"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) 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
[JIRA] [job-dsl-plugin] (JENKINS-28167) job-dsl-plugin fails to work on Jenkins ver. 1.557
Karel Striegel
created JENKINS-28167
job-dsl-plugin fails to work on Jenkins ver. 1.557
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
30/Apr/15 8:52 AM
Description:
Plugin install + restarted -> no issues.
Following the tutorial : https://github.com/jenkinsci/job-dsl-plugin/wiki/Tutorial---Using-the-Jenkins-Job-DSL
After coying the DSL exmaple Script block, and pressing save. I get the following error msg :
{Stack trace
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class javaposse.jobdsl.plugin.ExecuteDslScripts from {"scriptLocation":"true","scriptText":"job('DSL-Tutorial-1-Test') {\nscm {\ngit('git://github.com/jgritman/aws-sdk-test.git')\n}\ntriggers {\nscm('*/15 * * * *')\n}\nsteps {\nmaven('-e clean test')\n}\n}","targets":"","ignoreExisting":false,"removedJobAction":"","removedViewAction":"","lookupStrategy":"JENKINS_ROOT","additionalClasspath":"","stapler-class":"javaposse.jobdsl.plugin.ExecuteDslScripts","kind":"javaposse.jobdsl.plugin.ExecuteDslScripts"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
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
[JIRA] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Stefan Kalmelid commented on JENKINS-27588 Labels used in Label Factory are shown as not used A quick test in our playground environment looks fine, but it will have to wait a few weeks before it becomes live in the production environment. Thanks Domi! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Swapnil Kotwal commented on JENKINS-28099 Poll SCM not working I set logger with following params. hudson.triggers.SCMTrigger hudson.plugins.git.GitSCM hudson.scm.SCMDescriptor with log level all and set Poll schedule but still I can see following logs Apr 30, 2015 11:21:00 AM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@902791[PollSCm] Apr 30, 2015 11:21:00 AM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run Apr 30, 2015 12:11:00 PM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@902791[PollSCm] Apr 30, 2015 12:11:00 PM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run Apr 30, 2015 12:21:00 PM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@902791[PollSCm] Apr 30, 2015 12:21:00 PM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run Apr 30, 2015 12:31:00 PM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@902791[PollSCm] Apr 30, 2015 12:31:00 PM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [pollscm-plugin] (JENKINS-28099) Poll SCM not working
Swapnil Kotwal updated JENKINS-28099 Poll SCM not working Change By: Swapnil Kotwal (30/Apr/15 7:17 AM) Attachment: Capture.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
