[JIRA] (JENKINS-50200) Label accepts 2 groovy variables when using && but not || operator
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-50200
Label accepts 2 groovy variables when using && but not || operator
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-15 17:20
Priority:
Minor
Reporter:
Alex Taylor
When running a pipeline, the label expects a string with the option of an operator. Apparently the && operator with 2 groovy variables will evaluate correctly but not a || operator. So this pipeline runs correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 && groovyLabel2){
echo "hello"
}
But this code does not run correctly:
def groovyLabel1 = 'master'
def groovyLabel2 = 'TestAgent'
node(groovyLabel1 || groovyLabel2){
echo "hello"
}
because it fails with this error:
java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStep.label expects class java.lang.String but received class java.lang.Boolean
I think that groovy is doing some funky parsing here and causing the error because what should be the only thing allowed would be something
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor commented on JENKINS-49893 Re: Declarative directive snippet generator Andrew Bayer One other suggestion towards this issue would be to not have required "generated code" but maybe have inline help for the basics of the generation much like the Parallel step inside of the current Snippet Generator Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-49893 Declarative directive snippet generator Change By: Alex Taylor Attachment: Screen Shot 2018-03-15 at 4.59.02 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50222) Maven Metadata plugin does not iterate over credentials in folders
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50222 Maven Metadata plugin does not iterate over credentials in folders Issue Type: Bug Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2018-03-16 15:44 Priority: Major Reporter: Alex Taylor When using the Maven Metadata plugin, it does not pull credentials which are configured on folders and will only pull global credentials. An example resolved similar issue is https://issues.jenkins-ci.org/browse/JENKINS-34825 but that is on the P4 plugin Add Comment
[JIRA] (JENKINS-50326) Parameters with the same name as ENV variables overwrite the existing ENV variables
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50326 Parameters with the same name as ENV variables overwrite the existing ENV variables Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-21 19:32 Priority: Trivial Reporter: Alex Taylor When you have an existing ENV variable and then have a build with a parameter of the same name(even if different case) it will overwrite the ENV variable. Reproduction case: Create a global ENV variable called "FOO" and set it to "BAR" Create a test job "TestJob" Add a string parameter called "foo" to the job create a shell step to echo out the value of $FOO Run the job with TEST as the value of foo Observe that the output of the shell step is "TEST" instead of "BAR" Resolution: Personally I think freestyle jobs should call out if you want an ENV or parameter much like pipeline scripts do with the $param.VARIABLE. This will avoid the confusion entirely. Add Comment
[JIRA] (JENKINS-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Attachment: image001.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Issue Type: Bug Assignee: Unassigned Attachments: image001.png Components: blueocean-plugin Created: 2018-03-26 13:43 Priority: Minor Reporter: Alex Taylor Problem: When a pipeline builds a downstream job, there is not an easy way inside of blue ocean to navigate to that job(you have to go to the console log of the build and then click the downstream build link) Idea: It would be great if we could have a link in the pipeline flow UI(see attached) where the build link would either be clickable or there would be a new sub arrow which would give the downstream build links. Add Comment
[JIRA] (JENKINS-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor closed an issue as Duplicate Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT Mark Waite- I was finally able to reproduce this issue 100% if you have access to bitbucket. 1. Have Bitbucket repository with at least 10 branches 2. Create a freestyle job and configure it to use the git plugin but connect to a Bitbucket repository at `$BITBUCKET_URL/git/$PROJECT/$REPO.git` 3. Add a parameter called BRANCH and has the default value of ** 4. Use that parameter in the `Branches to build` section 5. Add a poll for changes of `* * * * *` so that it will build every minute 6. Add a shell step of something like "echo hello" 7. Run one build This will then launch a new build for every branch and then once that is done you will see it build every minute seeing changes. Let me know if that does not work for you because it has worked 2x for me so far. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50497 Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Issue Type: Bug Assignee: Devin Nusbaum Components: promoted-builds-plugin Created: 2018-03-30 15:48 Environment: Jenkins Core 2.107.x Promoted builds 3.0 + 3.1 Priority: Major Reporter: Alex Taylor Issue: When a user has full job permissions(build, create, promote) on Jenkins but not Overall Admin access, they can not manually promote a job using the button. Steps to reproduce: Spawn up a new Jenkins instance with 2 users: Admin(full admin permissions), Developer(full job permissions and overall read) and the promoted builds plugin installed Create a new job with a manual promotion process having no "Approvers" list Build the Job Observe that Admin can promote the build but Developer does not have access to the button to promote Workaround: Adding the Developer user to the list of approvers makes the button show up Expected Behavior: I would expect the Developer user to also have access to the promotion process since they have job promote permission Let me know if I can clarify anything
[JIRA] (JENKINS-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50497 Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Change By: Alex Taylor Attachment: Screen Shot 2018-03-30 at 12.03.39 PM.png Attachment: Screen Shot 2018-03-30 at 12.03.04 PM.png Attachment: Screen Shot 2018-03-30 at 12.02.06 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50497) Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list
Title: Message Title Alex Taylor commented on JENKINS-50497 Re: Manually triggered Promoted builds is not visible to users who are not Admins unless they are on the `Approvers` list Added a permissions matrix which includes Job Promote permission but there is no other "promote" permissions other than artifact promote: Screen Shot 2018-03-30 at 12.02.06 PM.png Admin user button: Screen Shot 2018-03-30 at 12.03.04 PM.png Dev user no button: Screen Shot 2018-03-30 at 12.03.39 PM.png Sorry for not adding that earlier Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50498) Invalid Object ID in remoting module related to Proxy methods
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50498 Invalid Object ID in remoting module related to Proxy methods Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-03-30 16:08 Environment: Remoting 3.14 Priority: Minor Reporter: Alex Taylor Exactly the same as https://issues.jenkins-ci.org/browse/JENKINS-23271 but with a slightly different stacktrace: 2018-03-27 13:08:51.899+ [id=4840845] SEVERE hudson.remoting.ExportTable#unexportByOid: Trying to unexport an object that's already unexported java.lang.Exception: Object appears to be deallocated at lease before Tue Mar 27 07:59:42 CDT 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) Caused: java.util.concurrent.ExecutionException: Invalid object ID 19 iota=20 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:516) at hudson.remoting.Channel.unexport(Channel.java:756) at hudson.remoting.Channel.unexport(Channel.java:746) at hudson.remoting.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:345) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(Callab
[JIRA] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor reopened an issue See my last comment since I think it is still an issue Jenkins / JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Change By: Alex Taylor Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, v
[JIRA] (JENKINS-50509) Docker Traceability plugin is affected by JEP-200
Title: Message Title Alex Taylor commented on JENKINS-50509 Re: Docker Traceability plugin is affected by JEP-200 Oleg Nenashev So then I should add a whitelist similar to https://github.com/jenkinsci/docker-plugin/pull/619/files and add the InspectContainerResponse to it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35269) Job configuration UI Layout is broken
Title: Message Title Alex Taylor commented on JENKINS-35269 Re: Job configuration UI Layout is broken Manuel Recena Soto Any ideas on the future PRs for this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41450) LDAP plugin supporting 2 completely different domains with separate Users and group searches
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-41450 LDAP plugin supporting 2 completely different domains with separate Users and group searches Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2017/Jan/25 7:06 PM Priority: Minor Reporter: Alex Taylor I would like to be able to have two completely differently structured AD domains inside of the LDAP plugin. It would be great to be able to have different group searches and Users associated with each domain in the LDAP plugin. So then it would traverse through one domain with a particular group search and User but when it searches through Domain 2 you can define a different user/group iteration. So everything under the `Advanced` tab inside the LDAP would be able to be replicated for each Domain. Is something like that possible? I could provide screenshots if this is unclear < /td> Add Comment
[JIRA] (JENKINS-41489) Credentials add menu should not check only global permissions
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-41489 Credentials add menu should not check only global permissions Issue Type: New Feature Assignee: Stephen Connolly Components: credentials-plugin Created: 2017/Jan/26 8:01 PM Priority: Minor Reporter: Alex Taylor The select helper should not only check global permissions for the add button here: https://github.com/jenkinsci/credentials-plugin/blob/ae658168e04b08116fd7831d3f2e58a6f07a69fa/src/main/resources/lib/credentials/select.jelly#L80 Add Comment
[JIRA] (JENKINS-41666) A badly configured cleartool command is unable to timeout inside Pipeline
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-41666
A badly configured cleartool command is unable to timeout inside Pipeline
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Feb/02 4:24 PM
Priority:
Major
Reporter:
Alex Taylor
If you call a poorly configured cleartool command from a pipeline job, timeout is unable to end the job when the timer is done. Steps to reproduce: -Ensure you have a slave(will work on ssh linux slave but I assume others could be the same) -Ensure the cleartool command line tool has been installed for use -Ensure you can access that cleartool command from Jenkins -Create a pipeline job -Create a timeout of something like 2 minutes Run something like /opt/rational/clearcase/bin/cleartool lsbl -fmt ""%Nd\n -stream $STREAM (lsbl: List baseline information per stream or component or by promotion level, fmt option to set the format, –str/eam stream-selector) this step will actually keep going indefinitely because it is a bad command since the format should be between the double quotes("$COMMAND") -Observe that even after 2 minutes the build is still going In order for the job to stop, both /abort and /kill have to be called. Expected results: I would normally expect that the timeout ends the job Possible causes: I think that cleartool is locking resources and not ending properly when asked to EDIT: This actually does not even need a badly configured command. Clearcase if told to timeout will never exit until it is done. So if your clear case command takes 30 seconds and you time it out at 15, it will show as taking 30 and never actually timing out. When it comes back it will then end the job because of a timeout call.
[JIRA] (JENKINS-41714) Docker Build and Publish Force Pull option needs to be changed
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-41714 Docker Build and Publish Force Pull option needs to be changed Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2017/Feb/03 8:54 PM Environment: Docker version 1.12.5 Priority: Minor Reporter: Alex Taylor For the Docker Build and Publish plugin, the `Force Pull` checkbox uses the --force option which has been deprecated in newer docker versions. Could we either remove that option or find a way around the --force no longer existing? Add Comment
[JIRA] (JENKINS-33941) When using a custom build directory, the renaming a job folder does not initially carry over previous builds
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-33941 When using a custom build directory, the renaming a job folder does not initially carry over previous builds Change By: Alex Taylor Summary: When using a custom build directory, the moving renaming a job folder does not initially carry over previous builds Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33941) When using a custom build directory, the renaming a job folder does not initially carry over previous builds
Title: Message Title Alex Taylor commented on JENKINS-33941 Re: When using a custom build directory, the renaming a job folder does not initially carry over previous builds OK so I think move/copy/promote is fixed now but renaming inside of core is not working. Kristin Whetstone Should I make a new defect for this? Clearly I initially reported it to be MCP but tagged it correctly in core. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41988) Subversion buildEnvVars does not load env variables in the svn URL for the warning
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-41988 Subversion buildEnvVars does not load env variables in the svn URL for the warning Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 2017/Feb/13 4:46 PM Priority: Minor Reporter: Alex Taylor Inside of src/main/java/hudson/scm/SubversionSCM.java the buildEnvVars() function does not load env variables corresponding to the svn URL. Therefore it throws a bunch of errors(no revision found corresponding to...) in the logs when you use something like $SVN_URL for the url in a job. I think just adding the function to load the build environment would solve this issue but maybe I am mistaken. I meant to get to this since similar fixes have been done elsewhere in the code but I have not yet spent the time. Add Comment
[JIRA] (JENKINS-42112) HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth)
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-42112 HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth) Issue Type: Bug Assignee: evernat Attachments: Screen Shot 2017-02-16 at 11.37.53 AM.png, Screen Shot 2017-02-16 at 11.41.05 AM.png Components: monitoring-plugin Created: 2017/Feb/16 4:50 PM Environment: Jenkins LTS 2.32.1.1 Monitoring 1.63.0 Priority: Minor Reporter: Alex Taylor The user generated in the HTTP session section reports as anonymous when using non-username/password style login methods. Steps to reproduce: 1. Download the Google Authorization plugin 2. Create a google authorization login(Screen Shot 2017-02-16 at 11.41.05 AM.png) 3. Login with said google account 4. Check the monitoring page under http sessions 5. Observe anonymous user(Screen Shot 2017-02-16 at 11.37.53 AM.png) This also affects the Cloudbees Operations Center to Enterprise communication where the Enterprise version shows anonymous user because it uses a token as well.
[JIRA] (JENKINS-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor reopened an issue So this defect was closed because it was thought to be caused by https://issues.jenkins-ci.org/browse/JENKINS-6644 but I am seeing that downgrading the build name setter plugin from 1.6.5 to 1.3 which means that it is probably caused by an issue specifically in this plugin. I think that JENKINS-6644 did lead in a good direction though. KK suggested "I recommend the use of ConcurrentHashMap instead of a plain HashMap to avoid concurrent update problems like this" in the old defect which I think is exactly the issue. Since the 1.3 version of build name setter EnvironmentVarSetter.java was added which calls `private final Map envVars = new HashMap();`. I think that just needs to be changed to ConcurrentHashMap and then this issue will be fixed. Thoughts? Jenkins / JENKINS-33527 Intermittent exception thrown when using plugin Change By: Alex Taylor Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Alex Taylor commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence Stephen Connolly I would say yes that could work fine if we had TCB enabled for pipeline. Do we need a separate defect for multibranch and TCB plugin or will the pipeline one suffice? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42309) Excessive calling of buildDependencyGraph can cause StackOverflow
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-42309 Excessive calling of buildDependencyGraph can cause StackOverflow Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 2017/Feb/24 5:00 PM Environment: Jenkins 1.651 template-project 1.5.2 Priority: Major Reporter: Alex Taylor I get a stack overflow when trying to calculate downstream dependencies because of the recursion that happens in buildDependencyGraph on large instances. This is not an easy issue to reproduce because it requires a large number of upstream and downstream jobs inside of the Jenkins instance. It seems like a similar issue happened with the Ivy plugin here: https://issues.jenkins-ci.org/browse/JENKINS-10025 The StackOverflow looks like: ``` 2017-02-22 14:45:21.410-0600 [id=133] WARNING j.u.ErrorLoggingScheduledThreadPoolExecutor#afterExecute: failure in task not wrapped in SafeTimerTask java.lang.StackOverflowError at nectar.plugins.rbac.groups.GroupContainerLocator$PersistenceHelper.getOrCreateGroupContainer(GroupContainerLocator.java:184) at com.cloudbees.hudson.plugins.folder.properties.FolderProxyGroupContainer$GroupContainerLocatorImpl.get(FolderProxyGroupContainer.java:230) at nectar.plugins.rbac.groups.GroupContainerLocator.locate(GroupContainerLocator.java:116) at nectar.plugins.rbac.strategy.RoleMatrixAuthorizationStrategyImpl.getACL(RoleMatrixAuthorizationStrategyImpl.java:181) at hudson.model.AbstractItem.getACL(AbstractItem.java:479) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:493) at com.cloudbees.hudson.plugins.folder.AbstractFolder.getItem(AbstractFolder.java:1156) at com.cloudbees.hudson.plugins.folder.AbstractFolder.getItem(AbstractFolder.java:140) at jenkins.model.Jenkins.getItemByFullName(Jenkins.java:2506) at
[JIRA] (JENKINS-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor commented on JENKINS-33527 Re: Intermittent exception thrown when using plugin Hey guys could I get you to try out this PR https://github.com/jenkinsci/build-name-setter-plugin/pull/14 to see if that fixes the serializable exception? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor commented on JENKINS-33527 Re: Intermittent exception thrown when using plugin Try out this PR to see if it solves the serializable issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33527) Intermittent exception thrown when using plugin
Title: Message Title Alex Taylor commented on JENKINS-33527 Re: Intermittent exception thrown when using plugin Lev Mishin So I was unable to reproduce locally but I may not have the scale to reproduce consistently. I wanted to see if other people could test it out. Otherwise it is a pretty simple change so I very much doubt it will cause issues. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Alex Taylor commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Jesse Glick, so I have a decently reproducible case for a freestyle job as well where docker-commons needs to be updated(either with the CLI or with changing the .dockercfg file). It seems that with the 1.12 version of docker they changed the file which is needed to log you in from ~/.dockercfg to ~/.docker/config.json which means that it will not see your credentials. So if you have a Private repo in dockerhub it will not log you in properly. Environment: Jenkins 2.32.3(but I think jenkins version is irrelevant) Docker-commons: 1.6 Docker version 1.12 on the machine running the job Docker build and publish:1.3.2 Steps to reproduce: Have a freestyle job Have a private dockerhub repository Have a step which is building a docker container and pushing it to that private dockerhub repo Behavior: It fails with a unauthenticated error because the ~/.dockercfg file no longer works. The docker build and publish step leverages the docker commons plugin to log into private repos so this is a good case to see the failure. Expected Behavior It would upload the docker container to your repo Workaround: If you log into that dockerhub repo through the CLI in a shell step before the build and publish step, it will create a ~/.docker/config.json file which will retain your credentials until the end of the build. Then the build and publish will work normally So I suppose we could potentially create both files as a temporary fix until we move to the CLI? What are your thoughts guys? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39445) Stage View adds extra whitespace for every Stage created
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-39445 Stage View adds extra whitespace for every Stage created Issue Type: Improvement Assignee: Sam Van Oort Attachments: Screen Shot 2016-11-02 at 11.02.58 AM.png Components: pipeline-stage-view-plugin Created: 2016/Nov/02 3:03 PM Environment: Jenkins version 2.7.4 Pipeline Stage view plugin version 2.1 Priority: Minor Reporter: Alex Taylor For every stage that is added to a pipeline, Stage view adds some extra whitespace at the very end of the stages. So it is not very noticeable with 1 stage but when you get 7 it becomes large. After 7 stages it stops existing because the stages properly fill the whole screen(at least at my resolution). Add Comment
[JIRA] (JENKINS-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title
Alex Taylor commented on JENKINS-45927
Re: CauseOfBlockage of items in Queue is extremely verbose
OK there is a way to workaround this issue by installing the Simple Theme Plugin which is to add a Theme Element of `Extra CSS` under `Manage Jenkins> Configre System` which contains the following data:
.build-details {
max-height:100px !important;
overflow: auto !important;
width:100% !important;
}
#tt {
overflow:hidden;max-height:200px;
}
This will restrict any pop up box to a certain size and truncate the rest which stops the UI from being blocked by this popup
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15445) DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor
Title: Message Title Alex Taylor commented on JENKINS-15445 Re: DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor Nicolas De Loof This PR does not seem to cause issues with the latest version of Jenkins anymore. Can we get it re-attempted or am I just missing something? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39403) Path separators in nested variables are not being escaped correctly when parsing the property file
Title: Message Title Alex Taylor commented on JENKINS-39403 Re: Path separators in nested variables are not being escaped correctly when parsing the property file I tried a fix in https://github.com/jenkinsci/envinject-plugin/pull/133 so please try it out to see if you see any obvious errors Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54501) ClassCastException in SonarUtils getPersistentActions
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-54501 ClassCastException in SonarUtils getPersistentActions Issue Type: Bug Assignee: Sonar Team Attachments: build.xml Components: sonar Created: 2018-11-06 21:22 Priority: Minor Reporter: Alex Taylor Issue: When iterating over all the actions within a Jenkins job using this code I hit a ClassCastException because getActions() does not necessarily return a class that can be converted to Action. This happened in particular with hudson.model.ParametersDefinitionProperty when I had a parameter in my build process. This issue is easily reproducible with the attached build.xml Steps to Reproduce: 1. Open up the Sonar plugin code in IDE of your choice 2. Do a mvn hpi:run and create a freestyle job 3. Build said freestyle job 2 times 4. Stop the run and then modify build #2's build.xml file with the attached 5. Restart the hpi:run 6. Observe the class cast error in the logs and the build #2 not show in the UI Expected results: The build.xml would throw other errors(like the sonar not existing) but be able to parse the build.xml Other Notes: I would normally expect the return for getActions() to be actionable items but apparently since it is deprecated the process has changed for what that will return. Additionally the getAllActions() method can not be used since it calls the overwritten createFor() which ends up causing a stackoverflow. There needs to either be a better checking on the getActions or the getActions needs to be replaced and the createFor() method needs to be fixed
[JIRA] (JENKINS-31561) WARNING: deprecated call to Run.getEnvironment
Title: Message Title Alex Taylor commented on JENKINS-31561 Re: WARNING: deprecated call to Run.getEnvironment I think the deprecated call is here: https://github.com/jenkinsci/parameterized-trigger-plugin/blob/2fa6c67baaeb53ebaddbb57952c939cf4711a02d/src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java#L291 I think it has to have the (listener) inside the call right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Alex Taylor commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type So I would think this could happen even with a slight disconnect of the slave per Ivan's last comment. Is there any more information that can be provided here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19170) Display all changes within a folder
Title: Message Title Alex Taylor commented on JENKINS-19170 Re: Display all changes within a folder Is this something which is still being looked at? Do we know if there are plans for a fix? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40957) More prominently offer option to opt out of anonymous usage statistics
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-40957 More prominently offer option to opt out of anonymous usage statistics Issue Type: New Feature Assignee: Unassigned Components: core Created: 2017/Jan/10 4:54 PM Priority: Minor Reporter: Alex Taylor I would like to add the ability to opt out of anonymous usage statistics inside the 2.x security setup screen instead of having to fully setup Jenkins and then go to Manage Jenkins>Configure system. Add Comment This message w
[JIRA] (JENKINS-40967) Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-40967 Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/10 9:07 PM Environment: Jenkins 2.19(but it works with any 2.0+) Web for Blue ocean 1.0.0-b14 Priority: Minor Reporter: Alex Taylor The link that gets added when loading the blue ocean plugins: "Open Blue Ocean" will not move if the searchbar+login name on the right become too large. So then they overlap and become unreadable. It would be great if the button would slide/shrink to ensure that anything near it is always clickable. Also sorry if I got the wrong component here Add Comment
[JIRA] (JENKINS-40967) Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-40967 Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big Change By: Alex Taylor Attachment: Screen Shot 2017-01-10 at 4.03.33 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40967) Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-40967 Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big Change By: Alex Taylor Attachment: Screen Shot 2017-01-10 at 4.03.27 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40967) Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-40967 Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big Change By: Alex Taylor Attachment: Screen Shot 2017-01-10 at 4.03.54 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40967) Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-40967 Open Blue Ocean link($JENKINS_URL/blue) does not move if the search bar or login name become too big Change By: Alex Taylor Attachment: Screen Shot 2017-01-10 at 4.03.27 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Component/s: quality-gates-plugin Component/s: sonar-quality-gates-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor reopened an issue Jenkins / JENKINS-47321 Quality Gates Sonarqube: projectKey Illegal character Change By: Alex Taylor Resolution: Won't Do Status: Closed Reopened Assignee: Rafael Ramos Ivana Sh Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47321) Quality Gates Sonarqube: projectKey Illegal character
Title: Message Title Alex Taylor commented on JENKINS-47321 Re: Quality Gates Sonarqube: projectKey Illegal character Ivana Sh Eleni Grozdani Dimitar Pop Dimitrov We had this issue on the wrong component(we thought it was the Sonar quality gates plugin). Would it be possible to take a look at https://github.com/jenkinsci/quality-gates-plugin/pull/57 and then potentially merge it? Seems like a quick win Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49701) Would like a new section of the Script security approval page to be "pending scripts from Disabled Jobs"
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-49701 Would like a new section of the Script security approval page to be "pending scripts from Disabled Jobs" Issue Type: New Feature Assignee: Andrew Bayer Components: script-security-plugin Created: 2018-02-22 17:15 Priority: Minor Reporter: Alex Taylor Request: Create a new section inside of the "In Process Script Approval" screen which shows pending approvals which are coming from disabled jobs Reasoning: There are some situations where you want to deny some scripts where developers are potentially doing bad things. But when Jenkins is restarted, those denied scripts come back to the "In Process Script Approval" screen which is annoying. It would be great to have a way to isolate those scripts which are not being fixed by developers. This could be accomplished by disabling their projects and then being able to sort their scripts so that new scripts waiting on approval are not lumped in with the bad ones on restart. Implementation: `ScriptApproval/index.jelly` could perhaps show a special UI for `PendingThing`s whose `context` has an `item` which is in fact a `disabled` `Job`. So this would mean creating a new UI box and putting scripts into it with the disabled job flag. Thoughts?
[JIRA] (JENKINS-47933) If Credentials are defined at a folder level, the Maven Artifact ChoiceListProvider plugin does not use them
Title: Message Title Alex Taylor commented on JENKINS-47933 Re: If Credentials are defined at a folder level, the Maven Artifact ChoiceListProvider plugin does not use them Stephan Watermeyer I was looking at other plugins that has this issue and found this PR which seems to iterate correctly. Maybe it is the included credentials plugin in your POM or the actual call you are making? Unfortunately that is for a pipeline step rather than a freestyle one but it may help. Otherwise I am not seeing anyone else who made the change. Any ideas Jesse Glick? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50995) Credentials scoped at a folder level return `Null` when used in a checkmarx build step
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50995 Credentials scoped at a folder level return `Null` when used in a checkmarx build step Issue Type: Bug Assignee: Sergey Kadaner Components: checkmarx-plugin Created: 2018-04-25 12:40 Priority: Major Reporter: Alex Taylor Issue: When you create a credential at a folder level and try to use it during a build with a checkmarx build step, the credential returns `null` value which fails to give access. Steps to reproduce: Create username/password combination which only exists at a folder level Create freestyle build with a checkmarx build step requiring authentication inside of that folder Choose that folder scoped username/password at the job level Run the build and check the checkmarx logs Observe that `Anonymous` is trying to get access rather than the username/password combination Workaround: You can scope the credentials at the global level and this will work 100% fine I did see another JIRA which was having the same issue and it was resolved with [this PR|https://github.com/jenkinsci/pipeline-aws-plugin/pull/16]. Maybe there is something helpful you can get there? It looks like the credentials plugin dependency was bumped to a newer version which is not included in checkmarx
[JIRA] (JENKINS-51146) Github Branch Source does not allow `#` character within branch names
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51146 Github Branch Source does not allow `#` character within branch names Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-05-04 20:11 Environment: Jenkins core at least 2.73.x LTS Github Branch source 2.3.0 Priority: Minor Reporter: Alex Taylor Something happened within the update of Github branch source plugin 2.3.0 update when combined with the update to Jenkins core 2.73.x where when you have a branch with a # character in the name it will not be able to find the branch name. Steps to recreate: Create a shared library with a branch name "Branch#Test" Attach that shared library to a Jenkins instance as a global library using the github modern SCM Create a job which loads the branch by doing @Library(SharedLibrary@Branch#Test) observe the job fails with No version Branch#Test found for library GithubLibrary This issue only happens when you update the github branch source plugin to newer than 2.3.0 and have a current version of core(from my testing) which means something in the 2.3.0 release changed this behavior. Let me know if I can provide more information
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-51404 processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-05-17 17:00 Environment: Jenkins Core 2.107.x Maven-pipeline 3.5.6 Priority: Minor Reporter: Alex Taylor Issue: When running a maven process inside of a build an error popped up saying java.lang.IllegalAccessError: tried to access method org.apache.xerces.parsers.XML11Configuration.getFeature0(Ljava/lang/String;)Z from class org.apache.xerces.parsers.XIncludeAwareParserConfiguration at org.apache.xerces.parsers.XIncludeAwareParserConfiguration.getFeature(Unknown Source) at org.apache.xerces.parsers.AbstractDOMParser.reset(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:97) at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050) It seems to come from the code here: https://github.com/jenkinsci/pipeline-maven-plugin/blob/1729e64250c10213ca428141092540bdeeaba97a/jenkins-plugin/src/main/java/org/jenkinsci/plu
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc The response was: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar So it does not seem too outdated(only 1 version back from what I can see). Should that be updated first? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Alex Taylor commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis I was looking into this issue and it appears that the Jacoco plugin fixed this issue for ENV variables with https://github.com/jenkinsci/jacoco-plugin/pull/74 but it does not actually parse the pom.xml for the `excludes`(or `includes` for that matter) configuration. Does that sound like the actual issue here rather than the Excludes not working at all? Did I miss anything here? I was going to work on getting this fixed with a PR hopefully within the next week Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-52943
Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-08-08 18:51
Environment:
Blue Ocean version 1.7.0
Priority:
Minor
Reporter:
Alex Taylor
Issue: When you have a shell step with either returnStdout or returnStatus being "true", the step does not show a preview like when those are not set to "true". Steps to Reproduce: Create a simple pipeline with the following definition:
node('master'){
sh 'echo "hello"'
sh returnStdout: true, script: 'echo "hello"'
sh returnStatus: true, script: 'echo "hello"'
}
And run the pipeline. Then look at it in Blue Ocean view and see that the first one has a description but the others do not.
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Title: Message Title Alex Taylor commented on JENKINS-15570 Re: Coverage report includes classes that have been excluded from Jacoco analysis Thanks for the update Gabriel Stanek just wanted make sure I was understanding everyone's issue and how best I can fix it Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc Did you get the chance to look at this further? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53134 Git checkout fails when using an SSH key with a passphrase Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-08-20 13:58 Environment: Jenkins core 2.121.2 and 2.107.x Git Plugin latest Git api latest Priority: Major Reporter: Alex Taylor Issue: A checkout from the master can not be performed when using a ssh key with a passphrase. It will hang on this step: > git fetch --tags --progress g...@github.com:alexanderrtaylor/support-kb-articles.git +refs/heads/*:refs/remotes/origin/* And eventually fail. Workaround: You can remove the passphrase and it will work normally Steps to reproduce: 1. Create a SSH key with a specific passphrase like `testing` and add it to Jenkins 2. Add ssh key to github 3. Create a job(freestyle or pipeline the behavior is the same) 4. Use the SSH key connect to the ssh location of the git url 5. Watch as the job fails. This works normally if I use a shell step to clone from the agent but the git plugin seems to be causing the issue
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark WaiteDevin Nusbaum This is MacOS and I see the same behavior as the customer who was running on windows >Are you using a passphrase which includes a character that is special to the shell Password was `testing` in my case I have not tried in Linux yet but I can certainly do it if you like. Could I attach a bundle of my instance where I reproduced so you can spin up a copy? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Devin Nusbaumsorry missed this. I used ssh with private key when I did my test. That is interesting about the setsid but I was not actually doing this checkout on an agent and was instead doing it on the master. Did you guys run it on the master as well? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark Waite Yeah I think the setsid is probably affecting me because I am running Jenkins from the terminal. But my question would be how do I go about adding setsid on a master? I could normally add it onto the prefix to the agent but if I am doing a checkout on master then how would I add it? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53326) SCM checkout needs to be able to refresh the checkout details
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53326 SCM checkout needs to be able to refresh the checkout details Issue Type: Improvement Assignee: Unassigned Components: workflow-scm-step-plugin Created: 2018-08-29 15:52 Priority: Minor Reporter: Alex Taylor Issue: I have a job where I am doing a simple checkout in a pipeline where I then make a modification to the git repo and push the update. This ends up causing a new build to be launched from either a webhook or polling event but it is a known good push done within the build process. Resolution: If there was a way to push which commitID the repo is associated with by doing something like a SCMrefresh step in a pipeline, it would help a new build not be triggered. I could stage the git commit locally to the workspace, update the commitID the job is "building", and then do the push which would stop a new build from triggering. This is especially useful for things like releases which a new build being triggered does not really make sense since all that was pushed is a new version number. Add Comment
[JIRA] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor assigned an issue to Mark Waite Jenkins / JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Change By: Alex Taylor Assignee: Nicolas De Loof Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Cyrille Le Clerc The output was this: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar Sorry for not giving this earlier! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-51404
processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Change By:
Alex Taylor
Comment:
[~cleclerc] The output was this:{code:java}class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar{code}Sorry for not giving this earlier!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53790 Kubernetes plugin shows failing templates to only admins Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-26 13:22 Priority: Major Reporter: Alex Taylor Background: With the advent of CJE2/Core on modern platforms, we started leveraging the Kubernetes plugin to define agents using kubernetes templates. This is a great new feature but allows non admins to generate new templates even within their pipelines. But since these non admins do not have access to the Kubernetes back end or the logging within Jenkins, they do not see when or why one of these templates fails Issue: When a non-admin user creates a k8s template which is badly formed they are unable to see that the container/pod is failing because it is just "waiting on $LABEL" Steps to reproduce: Create a pipeline job Create a template in that job with a badly defined docker image name Watch the job fail to start because it can not find its label If you are not an admin you can not see why the container/pod is failing to start because you can not access the k8s logs or the `Manage Jenkins> System Log` area of Jenkins to create a custom logger and see the cause for failure Resolution: We need a way in the job or similar to see why the container is failing to start, perhaps just a return code from Kubernetes. Or we need to not allow them to define templates on a job level so that non-admins can not create templates at all.
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title
Alex Taylor commented on JENKINS-53790
Re: Kubernetes plugin shows failing templates to only admins
Right now the only workaround is to do some strange-ness within a pipeline where you create a pipeline and parallel the template along with a groovy script(In my case I included it within a global shared library). So here are the steps I used: 1. Create a system log called "Kubernetes Log" with the `org.csanchez.jenkins.plugins.kubernetes` logger set to ALL 2. Create a pipeline job with a parallel statement which runs the template and loops through the following script until the template spins up:
import java.util.logging.Level
import java.util.logging.Logger
import hudson.logging.LogRecorderManager
import hudson.logging.LogRecorder
import java.util.logging.LogRecord
import hudson.util.RingBufferLogHandler;
def AgentName= searchString
List records = new ArrayList();
//Grabs the log manager
LogRecorderManager mgr = Jenkins.instance.getLog();
//Grabs the records
mgr.logRecorders.each{
if (it.getValue().getName() == "KubernetesLog")
{
records = it.getValue().getLogRecords()
}
}
//Iterates over the record messages looking for the agent name
for (LogRecord r : records) {
if (r.getMessage().contains(AgentName)){
println(r.getMessage().toString())
}
}
//Clears the logger
mgr.logRecorders.each{
if (it.getValue().getName() == "KubernetesLog")
{
it.getValue().doClear()
}
}
This will show the messages relating to `searchString` which should be the name of your template.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To un
[JIRA] (JENKINS-53820) If no Server Authentication Token is defined, it will cause builds to fail
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53820 If no Server Authentication Token is defined, it will cause builds to fail Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 2018-09-27 15:19 Environment: Sonar version 2.8.1 Priority: Major Reporter: Alex Taylor Issue: Under `Manage Jenkins > Configure system` if you leave the Server authentication token blank(which you theoretically can do because it says: SonarQube authentication token. Mandatory when anonymous access is disabled) it will cause builds which have sonar configured to fail in a very interesting way. The logs show a Null pointer with this stacktrace: 2018-09-27_08:09:48.63940 SEVERE: #2389 failed to build and we don't even have a listener 2018-09-27_08:09:48.63940 java.lang.NullPointerException 2018-09-27_08:09:48.63940 at hudson.plugins.sonar.SonarBuildWrapper.createLoggerDecorator(SonarBuildWrapper.java:149) 2018-09-27_08:09:48.63941 at jenkins.tasks.SimpleBuildWrapper.decorateLogger(SimpleBuildWrapper.java:192) 2018-09-27_08:09:48.63941 at hudson.model.Run.createBuildListener(Run.java:1827) 2018-09-27_08:09:48.63941 at hudson.model.Run.execute(Run.java:1708) 2018-09-27_08:09:48.63941 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) 2018-09-27_08:09:48.63942 at hudson.model.ResourceController.execute(ResourceController.java:97) 2018-09-27_08:09:48.63942 at hudson.model.Executor.run(Executor.java:429) But does not show a build log
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Alex Taylor commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" @Cyrille Return of the script is: class org.apache.xerces.jaxp.DocumentBuilderFactoryImpl (classLoader:AntClassLoader[/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/analysis-core.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-lang3-3.4.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/joda-time-2.9.5.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xml-apis-1.4.01.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/java2html-5.0.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/asm-3.3.1.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar]) -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar class org.apache.xerces.parsers.XIncludeAwareParserConfiguration (classLoader:AntClassLoader[/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/analysis-core.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/commons-lang3-3.4.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/joda-time-2.9.5.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xml-apis-1.4.01.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/java2html-5.0.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/asm-3.3.1.jar:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar]) -> file:/var/lib/jenkins/plugins/analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar class org.apache.xerces.parsers.XML11Configuration (classLoader:AntClassLoader[/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/cglib-2.2.2.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/groovy-sandbox-1.10.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/commons-beanutils-1.8.3.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/commons-digester3-3.2.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/findbugs.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/library-2.0.4.jar:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/asm-3.3.1.jar]) -> file:/var/lib/jenkins/plugins/findbugs/WEB-INF/lib/library-2.0.4.jar Let me know if that helps Add Comment
[JIRA] (JENKINS-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53944 Findbugs pulls in a very old Xerces library version Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2018-10-08 12:17 Priority: Minor Reporter: Alex Taylor Looking at the pom I can see that the findbugs plugin pulls in 2.9.1 of the xerces library. Is it possible to step this up to a newer version? This caused an issue in the pipeline maven plugin which was difficult to track down. Add Comment Thi
[JIRA] (JENKINS-53944) Findbugs pulls in a very old Xerces library version
Title: Message Title Alex Taylor commented on JENKINS-53944 Re: Findbugs pulls in a very old Xerces library version https://github.com/jenkinsci/findbugs-plugin/pull/16 to update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53960) Mac agents fail to connect on vSphere plugin
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-53960 Mac agents fail to connect on vSphere plugin Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2018-10-09 12:51 Environment: 2.121.x Jenkins LTS Latest vSphere plugin Priority: Minor Reporter: Alex Taylor Issue: I am successfully able to spin up a new agent with vSphere cloud if that agent is either a Linux or Windows machine but if the agent is a Mac agent, it is unable to spin up and connect back to Jenkins It appears to make the wrong API calls from what I can observe but I am not super familiar with how vSphere manages the Mac VMs Add Comment
[JIRA] (JENKINS-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title Alex Taylor commented on JENKINS-45927 Re: CauseOfBlockage of items in Queue is extremely verbose Daniel Beck would it not make more sense to just count the number of agents which do not have the label and then return that number? Then you could find out the names(if needed) from the build console log itself rather than from the hover over in the build queue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37893) When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-37893 When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order Issue Type: Bug Assignee: bap Components: flexible-publish-plugin Created: 2016/Sep/01 2:07 PM Environment: Jenkins ver. 1.651.3.1 Flexible Publish plugin ver. 0.15.2 Priority: Critical Reporter: Alex Taylor Issue: If you create 2 publisher templates, Publisher_A and Publisher_B, then try to use select Publisher_B inside of the `Add` section of the flexible publisher plugin it will revert back to Publisher_A once the configuration is saved. Steps to Reproduce: Create 2 new Publisher Templates: Publisher_A and Publisher_B Their transformer can be whatever you want as long as they save Create a new Freestyle project Create a post build action of Flexible Publish Add an Action under Conditional Action Select Publisher_B Save the configuration Go back into the configuration screen(or look at the config.xml) Check the action and it has reverted back to Publisher_A
[JIRA] (JENKINS-36450) Unable to inject HP Application AUtomation Tools properties with attributes/environment variables
Title: Message Title
Alex Taylor commented on JENKINS-36450
Re: Unable to inject HP Application AUtomation Tools properties with attributes/environment variables
Hey Roy, It would be great if you would extend the plugin to allow credentials to be passed to the HP plugin without exposing user name and password in the plugin at build step. Other plugins, such as SonarQube, Sonatype IQ Server plugin, are doing something like this. Or inject user id and password with environment variables, e.g. $ {almUserName} and $ {secret} rather than expose user name and password in the config.xml. It would help greatly in keeping our instance secure and allow credentials to be carried over to multiple jobs. I know this was not the original design but I would appreciate if we could add to the plugin to have this feature. We could easily change this to an RFE instead. Thanks!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37893) When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order
Title: Message Title Alex Taylor commented on JENKINS-37893 Re: When using Multiple Publisher Templates with Flexible publisher it will configure back to the one highest in Alphabetical order Sorry this may not actually be related to the Flexible Publisher plugin. I found out this same issue happens inside of the Build Timeout Plugin leading me to think it is an issue with templates and Publisher Templates specifically. Publisher Templates are from the CloudBees Templates plugin and seem to be the only ones that are sorted incorrectly. So maybe some sorting issues with the templates plugin specifically. I am going to leave this open until I am able to ask CloudBees developers to see where the issue may lie. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38355) Deleting an Upstream deployment allows a promoted build to continue without approval
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38355 Deleting an Upstream deployment allows a promoted build to continue without approval Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Sep/19 7:34 PM Environment: Jenkins ver. 1.651.3.1 Promoted Builds ver. 2.27 Priority: Major Reporter: Alex Taylor If you have a promoted build waiting on approval from 2 upstream deployments and then delete one of those upstream projects, it will allow the build to be promoted with only approving the other(non-deleted) deployment. Steps to reproduce: -Create 2 upstream projects Project A and B -Create a promoted build(downstream build) that depends on approval of A and B to complete -Run the downstream build -Observe it is waiting on A and B to build and be approved -Build A and B but dont approve either -Delete project A completely -Approve B -Observe the downstream build is completed Expected Results: For security reasons I would think this downstream build would need to be re-built before allowing it to be promoted. Additional thoughts: I would think this would also be reproduced if you only had 1 promoted upstream build that downstream build was waiting on and then deleted the upstream but I have not tested it.
[JIRA] (JENKINS-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38552 Multibranch pipeline (re)creation intelligence Issue Type: New Feature Assignee: Unassigned Components: workflow-multibranch-plugin Created: 2016/Sep/27 8:01 PM Priority: Minor Reporter: Alex Taylor When a multibranch pipeline is created or recreated, it instantly pulls in all the branches at once and starts initial builds on them. Could we have a way to limit the number of builds which happen right at branch creation? Something user configurable would be great. Add Comment
[JIRA] (JENKINS-38612) With the new Timezone expression in Cron, should the help tab not reflect the timezone listed in the expression?
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38612 With the new Timezone _expression_ in Cron, should the help tab not reflect the timezone listed in the _expression_? Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-09-29 at 11.55.24 AM.png Components: core Created: 2016/Sep/29 4:00 PM Priority: Minor Reporter: Alex Taylor When using the TZ _expression_ in Cron I was thinking that when you navigate away and it gives you the message when it would have last run(ex: Would last have run at Thursday, September 29, 2016 11:55:02 AM EDT; would next run at Thursday, September 29, 2016 11:55:02 AM EDT.), I think that it should reflect that Timezone that is listed in the _expression_ rather than the current Jenkins one right? In the screenshot I have a TZ of Los Angeles but my Jenkins is configured to be EDT I would think it should reflect PDT instead since I changed the timezone. Add Comment
[JIRA] (JENKINS-38615) Add user information to the restart checkbox after updating plugins
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-38615 Add user information to the restart checkbox after updating plugins Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Sep/29 7:34 PM Priority: Minor Reporter: Alex Taylor We would like to have the information of the user who hit the checkbox in the "Restart Jenkins when installation is complete and no jobs are running" that comes up after plugin updates. Any other time someone calls a restart, the user name gets recorded in the logs so it would be nice to get it for this one too. Add Comment
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-34861 Job Config History Plugin failing when comparing diff between config files Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/May/16 7:54 PM Labels: security-170 Priority: Critical Reporter: Alex Taylor Job config history plugin is failing when comparing the differences between 2 config pages with a null pointer error which appears to be a crumb issue. It seems to be related to security-170 release form 1.651.2. Actual error shown below: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:8
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Alex Taylor commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files Upgrading to 2.13 solved the issue so I think this can be set to resolved. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-35497) If a docker image already exists, Docker Custom Build Environment will not pull a newer version of the image
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-35497 If a docker image already exists, Docker Custom Build Environment will not pull a newer version of the image Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 2016/Jun/09 1:57 PM Priority: Major Reporter: Alex Taylor While using Docker Custom Build Environment plugin, if an image already exists on a slave, it will not pull that image again even if that potential pulled image is newer than the one on the slave. This means that newer docker images will never be pulled so the image has to be forcibly deleted and then re-pulled. Add Comment
[JIRA] (JENKINS-36251) Add Labels to the Build Executor Status screen
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-36251 Add Labels to the Build Executor Status screen Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-06-27 at 4.18.04 PM.png Components: core Created: 2016/Jun/27 8:22 PM Priority: Minor Reporter: Alex Taylor I would like to add a column for Label names inside of the Build Executor Status screen to more easily see how slaves are broken up and what label they are associated with. Add Comment
[JIRA] (JENKINS-36992) Config History Plugin does not show history of Deleted slaves in the UI
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-36992 Config History Plugin does not show history of Deleted slaves in the UI Issue Type: New Feature Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/Jul/27 1:19 PM Environment: JobConfigHistory-plugin v2.12 Labels: jobconfighistory Priority: Minor Reporter: Alex Taylor I would like Job Config History Plugin to show the config history of deleted slaves(specifically that they were deleted). It appears the plugin does actually have the config history in the filesystem but it will not display that on the UI. It would be great if we could have a section in the UI of the history of slaves which would show all the deleted slave configs including that they were deleted. Add Comment
[JIRA] [workflow-plugin] (JENKINS-33458) Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-33458 Feature Request: Make Sidebar-Link Plugin Compatible With Pipeline Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 10/Mar/16 3:34 PM Environment: Jenkins version 1.625.x.x Sidebar plugin 1.7 Build Pipeline plugin 1.5.1 Labels: workflow Priority: Minor Reporter: Alex Taylor Please make the Sidebar-Link Plugin compatible with the pipeline plugin by adding the sidebar link access to pipeline jobs. https://wiki.jenkins-ci.org/display/JENKINS/Sidebar-Link+Plugin
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33589) Parallel Pipeline Jobs Hang on Resume
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-33589 Parallel Pipeline Jobs Hang on Resume Issue Type: Bug Assignee: Antonio Muñiz Components: pipeline-stage-view-plugin Created: 16/Mar/16 1:12 PM Environment: Jenkins ver. 1.642.2.1 Build Pipeline Plugin 1.5.1 Delivery Pipeline Plugin 0.9.8 Priority: Minor Reporter: Alex Taylor Issue: A job is created with a parallel section in the pipeline code. Then when that pipeline is being built, if the Jenkins instance is reset, the resume feature will restart the pipeline code but the UI will show that the build never progresses or completes. Steps to Reproduce: -Create a pipeline job -Put parallel section into the pipeline script -Build job -Restart Jenkins instance from JOC or manual methods while the job is building -Observe the script does actually finish but the UI shows it as still building and making no progress Proposed Resolution: Ensure the UI is actually catching up with the script(because it shows "Success") and that the pipeline and build view loading bars are making progress
[JIRA] [core] (JENKINS-33941) When using a custom build directory, the moving a job folder does not initially carry over previous builds
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-33941 When using a custom build directory, the moving a job folder does not initially carry over previous builds Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/31 2:32 PM Priority: Minor Reporter: Alex Taylor If someone is using a custom build directory, when trying to move Jobs between folders it will not carry over the build history until the configuration is edited and saved. So with every job that is moved using either the move/copy/promote or moving it inside of the file system they have to hit Configure then save in order to see previous build info. Add Comment
[JIRA] [serenity-plugin] (JENKINS-34030) Custom Screen Resolution on Serenity Plugin
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-34030 Custom Screen Resolution on Serenity Plugin Issue Type: Bug Assignee: Unassigned Components: serenity-plugin Created: 2016/Apr/05 1:09 PM Priority: Minor Reporter: Alex Taylor The Serenity Plugin has a hard coded display size for the build information. I wanted to see if I could get it updated to be scaling so that it would allow for custom screen resolutions. Or just allow it to be a configurable setting somehow. Add Comment
[JIRA] [docker-plugin] (JENKINS-34238) Flyweight Job Support For Docker Plugin
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-34238 Flyweight Job Support For Docker Plugin Issue Type: New Feature Assignee: magnayn Components: docker-plugin Created: 2016/Apr/14 1:15 PM Environment: Build enviornment: Jenkins ver. 1.625.3.2 (CloudBees Jenkins Enterprise 15.11) docker-plugin 0.16.0 Priority: Minor Reporter: Alex Taylor When building a Matrix project we would like to be able to have the build spin up docker containers for each flyweight task that the matrix project creates. I would like to set master executors to 0 and only allow building inside of docker containers. So each task would create a container and the execute inside of that container. I would like to remain more flexible with matrix builds and be able to adjust my build environment to suit what the build is actually doing.
[JIRA] [docker-workflow-plugin] (JENKINS-34286) Canceling build in the middle of pulling large image from private repository will not allow a future build to happen
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-34286
Canceling build in the middle of pulling large image from private repository will not allow a future build to happen
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
2016/Apr/15 6:13 PM
Environment:
Jenkins ver. 1.642.4.1 CloudBees Docker Pipeline 1.4
Priority:
Major
Reporter:
Alex Taylor
Issue: Canceling a build while pulling a large docker image from a private repository will stall future builds waiting on the first canceled build to "finish" pulling the image which it never does.
Steps to Reproduce: -Have private docker image repository -Create pipeline job with docker.image('$WHATEVER'){} where $whatever is a large image(to give you more time) -Run said pipeline job -Cancel pipeline job with Red X in the UI during the download of the image from the repository -Try to rebuild on the same node -Observe the build waiting on the image from the previous build to download but it never does
Suggested Resolution: -Maybe at the time of canceling the build the docker image that is half downloaded could be stopped and wiped?
[JIRA] [workflow-plugin] (JENKINS-34716) Add REST API polling to Pipeline
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-34716 Add REST API polling to Pipeline Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/10 6:42 PM Priority: Minor Reporter: Alex Taylor I would like to have the ability to force a poll of a pipeline job using the REST API. Where it would be something like curl -X POST $JENKINS_URL/jobs/$PIPELINE_JOB/polling and that would force a poll check on the job itself. Add Comment
[JIRA] (JENKINS-48161) Deadlock caused by synchronized methods in EC2Cloud
Title: Message Title Alex Taylor commented on JENKINS-48161 Re: Deadlock caused by synchronized methods in EC2Cloud Andrea Vavassori This very much looks like JENKINS-53858 which was resolved in 1.42. Could I get you to compare that JIRA with your current one and see if it is the same thing? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Issue Type:
Bug
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2019-02-22 16:40
Priority:
Major
Reporter:
Alex Taylor
Issue: When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins. Steps to reproduce: 1. Create a job with an Ansible Tower step 2. Inside of that step call an ansible script which uses the suggested line:
- name: Set a Jenkins variable
debug:
msg: "JENKINS_EXPORT VAR_NAME=value"
3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage 4. Observe the variable comes back as "null" I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not work Expected Result: I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Change By:
Alex Taylor
Issue:When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins.Steps to reproduce:1. Create a Pipeline job with an Ansible Tower step2. Inside of that step call an ansible script which uses the suggested line:{code:java} - name: Set a Jenkins variable debug:msg: "JENKINS_EXPORT VAR_NAME=value"{code}3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage4. Observe the variable comes back as "null"I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not workExpected Result:I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2020-03-19 16:43
Priority:
Minor
Reporter:
Alex Taylor
Issue: In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build. Steps to reproduce: Create a pipeline with this as the definition:
pipeline {
agent any
checkout
stages {
stage('Build') {
steps {
echo "hello"
}
}
stage('Test') {
steps {
echo "hello"
}
}
stage('Deploy') {
steps {
echo "hello"
}
}
}
}
Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Expected results: The stage view page correctly shows the build status being failed. The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: Alex Taylor Attachment: Screen Shot 2020-03-19 at 12.43.38 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205288.1584636193000.9685.1584636300325%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Change By:
Alex Taylor
Issue:In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build.Steps to reproduce:Create a pipeline with this as the definition:{code:java}pipeline {agent any checkoutstages {stage('Build') { steps { echo "hello"}}stage('Test') { steps { echo "hello"}}stage('Deploy') { steps { echo "hello"}}}}{code}Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Build 203 looks correct and build 204 is the one with the incorrect status indicator: !Screen Shot 2020-03-19 at 12.43.38 PM.png|thumbnail! Expected results:The stage view page correctly shows the build status being failed.The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
