[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Steve Jansen commented on JENKINS-21750 Re: Promoted Builds Plugin Hi, Option #4: We release the plugin as an out of band hpi file as a GitHib Release. We use the existing GH repo. I've had a few people stumble on my ancient hpi which uses this distributions method. We could add the URI to install the hpi in the DSL docs (which are outstanding). Having hard data on community downloads for a new plugin might sway the minds of more senior CloudBees team members. Warm regards, Steve 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] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Steve Jansen commented on JENKINS-21750 Re: Promoted Builds Plugin Dennis Schulte Perhaps a pragmatic alternative is to ship the job-dsl-promotions-plugin as a jar inside the hpi for the dsl plugin? You still get separation of the code bases. Definitely not ideal, but, would work for end users. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-26779) Git repo URL 404s cause null reference exception and a UI 500 response
Steve Jansen commented on JENKINS-26779 Git repo URL 404s cause null reference exception and a UI 500 response Just found this is a duplicate of JENKINS-24383 See https://github.com/jenkinsci/github-oauth-plugin/pull/32 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Steve Jansen commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin Related to JENKINS-26779 @Sam what's your thoughts on the PR? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Steve Jansen commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Daniel Beck: my fix resolved the safeRestart (and restart) issue on my CentOS 6.5 system (which curiously uses the Oracle JDK 1.7.0_65). This resolved the Failed to obtain the command line arguments of the process error seen on my system in both the Jenkins Web UI and the Jenkins SSH/CLI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Steve Jansen commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart I believe I figured this out. After experiencing this problem on a CentOS 6.5 VM, I decided to start the Jenkins server interactively (eg., java -jar jenkins.war ... ) I saw a very curious warning: Nov 21, 2014 10:46:51 PM jenkins.diagnosis.HsErrPidList init WARNING: Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: /tmp/jna/jna4408307760862063272.tmp: /tmp/jna/jna4408307760862063272.tmp: failed to map segment from shared object: Operation not permitted This reminded me of a very similar problem on CentOS 6.5 with ruby-build that I documented @ https://github.com/sstephenson/ruby-build/issues/604#issuecomment-54310466 The cause seems to be when $TMPDIR is mounted as noexec. Just re-mount your temp dir and tmpfs as executable: $ mount /dev/mapper/vglocal20140828-root00 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,noexec,nosuid,nodev) /dev/sda1 on /boot type ext3 (rw) /dev/mapper/vglocal20140828-tmp00 on /tmp type ext4 (rw,noexec,nosuid,nodev) /dev/mapper/vglocal20140828-log00 on /var/log type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) I was able to resolve by removing the noexec option from /tmp and tmpfs and re-mounting both: $ cp /etc/fstab /tmp/~fstab $ sudo vi /etc/fstab $ diff /tmp/~fstab /etc/fstab 11c11 /dev/mapper/vglocal20140828-tmp00 /tmp ext4 defaults,nosuid,nodev,noexec 1 2 --- /dev/mapper/vglocal20140828-tmp00 /tmp ext4 defaults,nosuid,nodev 1 2 14c14 tmpfs /dev/shm tmpfs defaults,nosuid,nodev,noexec 0 0 --- tmpfs /dev/shm tmpfs defaults,nosuid,nodev 0 0 $ sudo mount -o remount /tmp $ sudo mount -o remount tmpfs $ mount /dev/mapper/vglocal20140828-root00 on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) /dev/sda1 on /boot type ext3 (rw) /dev/mapper/vglocal20140828-tmp00 on /tmp type ext4 (rw,nosuid,nodev) /dev/mapper/vglocal20140828-log00 on /var/log type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Steve Jansen commented on JENKINS-21750 Promoted Builds Plugin @Thomas, my understanding is the external config files exist because each promotion is really a child job in Jenkins, and child jobs have their own config, history, etc. This makes sense when you start to think about how a promotion with manual approval would be hard to implement in a single job config. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Steve Jansen commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Confirmed reverting to 2.16 fixes the problem for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Steve Jansen commented on JENKINS-21750 Promoted Builds Plugin For community visibility, I recently rebased Thomas' pull request with the lastest updates to the plugin and added a small fix. This PR is now able to merge Thomas' work into master: https://github.com/jenkinsci/job-dsl-plugin/pull/291 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Steve Jansen commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Hi Daniel Daniel, I'd love to use a more specific firewall rule. Re: the Configure Global Security port, I think that port is only for JNLP. I have the default setting to use a random port for JNLP. Does a static port for JNLP also effect the CLI? That probably makes sense for the CLI to use JNLP... Cheers, Steve This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Steve Jansen commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Not sure if this helps or not, but I faced a similar issue with this network topology: LAN A (OpenStack cluster with a 192.168.2.0/24 internal network, NAT'd to the rest of the LAN via the 10.166.140.0/24 "floating" IPs) Jenkins master @ 192.168.2.10 or 10.166.140.10 Jenkins slave 1 @ 192.168.2.11 Jenkins slave 2 @ 192.168.2.12 LAN B (3rd party data center, connected to LAN A via site-to-site VPN) Jenkins slave 3 @ 10.21.26.50 Jenkins slave 4 @ 10.21.26.51 The CLI worked fine over the master node's private ip address, e.g. `java -jar jenkins-cli.jar -s http://192.168.2.10:8080/ help` The CLI failed on any slave in either LAN when using the master node's public ip address, e.g., `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` raised the error "SEVERE: I/O error in channel Chunked connection" The problem was ultimately the software firewall in the OpenStack cluster that only applied to the floating IPs (e.g., 10.166.140.0/24). The resolution was to allowing UDP ingress on ports 1024-65535 and TCP ingress on ports 1024-65535 for my slaves public IPs (10.21.26.0/24 and 10.166.140.0/24). Executing `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` then worked as expected on all slaves in both data centers. My $0.02 - there is some complex networking for CLI connections: there seems to be ICMP, UDP, and TCP in use at the same time, along with random (JNLP?) ports on the server. The CLI client could use connectivity checks and/or clearcut error messages to better explain when connectivity fails for a specific protocol/address/port. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Steve Jansen edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Not sure if this helps or not, but I faced a similar issue with this network topology: LAN A (OpenStack cluster with a 192.168.2.0/24 internal network, NAT'd to the rest of the LAN via "floating" public IPs on 10.166.140.0/24) Jenkins master @ 192.168.2.10 or 10.166.140.10 Jenkins slave 1 @ 192.168.2.11 Jenkins slave 2 @ 192.168.2.12 LAN B (3rd party data center, connected to LAN A via site-to-site VPN which NAT to 10.21.26.0/24 on LAN A) Jenkins slave 3 @ 10.21.26.50 Jenkins slave 4 @ 10.21.26.51 The CLI worked as expected when using the master node's private ip address but not the master node's public ip address. For example `java -jar jenkins-cli.jar -s http://192.168.2.10:8080/ help` worked, but `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` raised the error "SEVERE: I/O error in channel Chunked connection" on any slave. The problem was ultimately the software firewall in the OpenStack cluster that only applied to the floating IPs (e.g., 10.166.140.0/24). The resolution was to allowing UDP ingress on ports 1024-65535 and TCP ingress on ports 1024-65535 where the destination was the Jenkins master node and the source was my slaves public IPs (10.21.26.0/24 and 10.166.140.0/24). After the firewall change, executing `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` worked as expected on all slaves in both data centers. My $0.02 - there is some complex networking for CLI connections: there seems to be ICMP, UDP, and TCP in use at the same time, along with random (JNLP?) ports on the server. The CLI client could use connectivity checks and/or clearcut error messages to better explain when connectivity fails for a specific protocol/address/port. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen updated JENKINS-16297 FATAL: Could not apply tag [project name]test-17 Change By: Steve Jansen (25/Jul/14 12:12 AM) Attachment: screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen resolved JENKINS-16297 as Not A Defect FATAL: Could not apply tag [project name]test-17 See comments. Change By: Steve Jansen (25/Jul/14 12:12 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen commented on JENKINS-16297 FATAL: Could not apply tag [project name]test-17 This is not a bug in Jenkins. Git is complaining that you have not configured your username/email address. See https://help.github.com/articles/setting-your-email-in-git This can be configured globally for the Jenkins user identity, or you can configure per job by clicking "SCM Git Additional Behaviours" and adding the custom username/email address behaviour. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-16297) FATAL: Could not apply tag [project name]test-17
Steve Jansen edited a comment on JENKINS-16297 FATAL: Could not apply tag [project name]test-17 Closing - not a defect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Steve Jansen commented on JENKINS-23662 Github Plugin 1.9 broke webhook trigger Duplicate of JENKINS-23661 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23661) github webhook failing
Steve Jansen commented on JENKINS-23661 github webhook failing Good news, it looks like the GitHub service for the "Jenkins (GitHub plugin)" was just updated. The change @ https://github.com/github/github-services/blame/master/lib/services/jenkins_github.rb#L16 looks like it will fix this problem for the plugin v1.9. I'm not sure if this change is live on GitHub.com, or if you will need to recreate the Jenkins service on the "Webhooks Services" setting panel @ https://github.com/:org-or-user/:repo/settings/hooks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23661) github webhook failing
Steve Jansen commented on JENKINS-23661 github webhook failing Also occurring on Jenkins LTS 1.554.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23661) github webhook failing
Steve Jansen commented on JENKINS-23661 github webhook failing Believe this commit in the GitHub-Plugin v1.9 has broken webhooks when using the GitHub "service" for Jenkins rather than a GitHub "webhook" with your Jenkins webhook URL. https://github.com/jenkinsci/github-plugin/commit/bcc3bc1ca704b2be3f1475b616fa1b209986a1fd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23661) github webhook failing
Steve Jansen updated JENKINS-23661 github webhook failing Change By: Steve Jansen (03/Jul/14 1:35 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23353) Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link
Steve Jansen created JENKINS-23353 Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link Issue Type: Bug Affects Versions: current Assignee: Patrik Boström Components: delivery-pipeline Created: 06/Jun/14 10:18 PM Description: Overview Pull Request #67 added the ability to use a Delivery Pipeline view as the default view in Jenkins (see JENKINS-23282). However, this fix introduced a defect when trying to create a new job from the default view. Steps to Reproduce --- 1. As a Jenkins admin, install version 0.8.0 or later of the Delivery Pipeline plugin in Jenkins 2. Create a new pipeline view by navigating to /newView in Jenkins, selecting "Build Pipeline View", assigning a name, and clicking "Ok" 3. In the newly created view from #2, click the "Edit View" sidebar link to add one or more jobs to the pipeline view. Click Ok to save the changes to the pipeline view. 4. Click the "Manage Jenkins" sidebar link, and click the "Configure System" link. 5. Change the default view to the pipeline view created in step #2. Click Ok to save. 6. Navigate to the Jenkins default view by clicking the Jenkins logo in the upper left hand header region of the screen 7. Click the "New Item" sidebar link to create a new job. 8. Enter a new job name such as "test", select "Build a free-style software project", and click the "OK" button. Expected Result --- Jenkins should create a new job using the name provided in step #8 and render the configure page for the new job. Actual Result - An error page displays with a stack trace of javax.servlet.ServletException: java.lang.StackOverflowError ... Caused by: java.lang.StackOverflowError at hudson.model.ViewGroupMixIn.getPrimaryView(ViewGroupMixIn.java:127) at jenkins.model.Jenkins.getPrimaryView(Jenkins.java:1484) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) ... Remarks --- The hudson.model.View abstract class declares the doCreateItem method as abstract. The current implementation of doCreateItem in the DeliveryPipelineView class defers implementation of doCreateItem to the default system view. This causes an infinite loop when the DeliveryPipeline view is the default view, as it keeps calling it's own doCreateItem method. Project: Jenkins Labels: plugin Priority: Minor Reporter: Steve Jansen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23282) Delivery Pipeline view renders a blank page when set as the default system view in Jenkins
Steve Jansen created JENKINS-23282 Delivery Pipeline view renders a blank page when set as the default system view in Jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: delivery-pipeline Created: 03/Jun/14 4:22 AM Description: Overview The Delivery Pipeline view renders a blank page when configured as the default system view. Steps to Reproduce --- 1. As a Jenkins admin, install version 0.8.0 or earlier of the Delivery Pipeline plugin in Jenkins 2. Create a new pipeline view by navigating to /newView in Jenkins, selecting "Build Pipeline View", assigning a name, and clicking "Ok" 3. In the newly created view from #2, click the "Edit View" sidebar link to add one or more jobs to the pipeline view. Click Ok to save the changes to the pipeline view. 4. Click the "Manage Jenkins" sidebar link, and click the "Configure System" link. 5. Change the default view to the pipeline view created in step #2. Click Ok to save. 6. Navigate to the Jenkins default view by clicking the Jenkins logo in the upper left hand header region of the screen Expected Result --- The default view in Jenkins should render the same way as the result of step #3 Actual Result - The default view is blank. Remarks --- The pipeline view is still available and functioning properly by navigating to the /view/All URL. The XHR calls to the delivery pipeline view api do not work when the view is the default view; this is due to the use of 'api/json' as the api url. The root level http://server/JenkinsRootUrl/api/json URL is reserved for the JSON API for jobs entities. Project: Jenkins Labels: plugin Priority: Major Reporter: Steve Jansen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23282) Delivery Pipeline view renders a blank page when set as the default system view in Jenkins
Steve Jansen commented on JENKINS-23282 Delivery Pipeline view renders a blank page when set as the default system view in Jenkins Pull request @ https://github.com/Diabol/delivery-pipeline-plugin/pull/67 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-17171) Token macro expansion not working in Groovy plugin 1.13
Steve Jansen commented on JENKINS-17171 Token macro expansion not working in Groovy plugin 1.13 @Slawomir - I packaged this as a GitHub pull request See https://github.com/jenkinsci/groovy-plugin/pull/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-21009) Allow manual trigger
Steve Jansen commented on JENKINS-21009 Allow manual trigger Hi Patrick, +1 for trying out the branch to manually trigger downstream projects/steps. Manual steps are important for new shops starting out with CD. Cheers! Steve This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth] (JENKINS-16350) logout link doesn't work
Steve Jansen commented on JENKINS-16350 logout link doesnt work @kohsuke - I am also effected by this issue. I looked into the GitHub OAuth API v3 web application flow @ https://developer.github.com/v3/oauth/#web-application-flow . I could not find a way to logout the current user or otherwise forcibly revoke the OAuth token. It seems the only way to do this is to navigate to https://github.com/settings/applications and click "Revoke" under the applicable entry in the "Authorized Applications" section. As a workaround, would you please point me in the right direction on how I could modify the github-oauth plugin to disable display of the "logout" link in the web ui? I'm happy to create a patch for this, however, I'm still new to the Jenkins source tree and don't know where to start with this change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
