[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set
Title: Message Title Raphael Baron commented on JENKINS-50328 Re: Pipeline editor not working if Script Path is set I'm experiencing the same issue. My use case is: I have a monorepo with independent pipelines (different Jenkinsfiles) on two subdirectories. Both pipelines run fine and show the correct step in blue ocean. Only the editor doesn't seem to recognize the Jenkinsfiles - it shows an empty view when you try to edit any of them. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189375.152167439.1571.1562224320322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58336) ERROR: Exception reading response javax.mail.MessagingException: Exception reading response
Title: Message Title yang zz created an issue Jenkins / JENKINS-58336 ERROR: Exception reading response javax.mail.MessagingException: Exception reading response Issue Type: Bug Assignee: David van Laatum Attachments: first.png, job send fail.png, second fail msg .txt, second.png Components: email-ext-plugin Created: 2019-07-04 07:17 Environment: Jenkins ver. 2.150.1 Email Extension 2.66 & 2.57.2 Labels: email-ext email Priority: Blocker Reporter: yang zz When the job ends triggering the message, it is occasionally sent successfully, and occasionally the transmission fails. I found that the mailbox server authentication needs to be re-authenticated after 30s, and the email-ext-plugin timeout is 60s; In the system management, the first time the email was sent successfully, The second time the mail is sent is between the mailbox server authentication requires re-authentication and the email-ext-plugin has not timed out, and the mail fails to be sent.
[JIRA] (JENKINS-58337) Promotion Console Log
Title: Message Title Felipe Leite created an issue Jenkins / JENKINS-58337 Promotion Console Log Issue Type: Bug Assignee: Oleg Nenashev Attachments: image-2019-07-04-17-16-27-449.png Components: promoted-builds-plugin Created: 2019-07-04 07:18 Priority: Minor Reporter: Felipe Leite Promotion console log is showing build log. This started to happen after the plugins update I did. Add Comment
[JIRA] (JENKINS-58336) ERROR: Exception reading response javax.mail.MessagingException: Exception reading response
Title: Message Title yang zz updated an issue Jenkins / JENKINS-58336 ERROR: Exception reading response javax.mail.MessagingException: Exception reading response Change By: yang zz When the job ends triggering the message email ,it is occasionally sent successfully, and occasionally the transmission fails.I found that the mailbox server authentication needs to be re-authenticated after 30s,and the email-ext-plugin timeout is 60s;In the system management,the first time the email was sent successfully,The second time the mail is sent is between the mailbox server authentication requires re-authentication and the email-ext-plugin has not timed out, and the mail fails to be sent. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200448.1562224624000.1584.1562225100453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Vladimir Eremeev commented on JENKINS-57502 Re: Cmake arguments sometimes are added to path in parallel build The problem has gone. Jenkins version was updated to 2.176.1 Cmake plugin version is 2.6.1 Cmake program version is 3.13 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199365.1557999255000.1586.1562225520155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Maxime KILT edited a comment on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step I don't think username/password are necessary when using a token for our incoming webhook . What are they for anyway? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1589.1562226540288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Maxime KILT commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step I don't think username/password are necessary when using a token. What are they for anyway? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1588.1562226540274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title
Maxime KILT edited a comment on JENKINS-58315
Re: Allow to customize serverUrl while using rocketSend step
I don't think username/password are necessary when using a token for our incoming webhook. What are they for anyway? For info, today we use the [Slack plugin|https://github.com/jenkinsci/slack-plugin#security] in a roundabout way for RocketChat but we cannot user the latest version:{code:java}slackSend(channel: 'jenkins',message: 'my message',baseUrl: 'https://myrocket.example.com/hooks/',teamDomain: 'myrocket',token: '0123456789'){code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1594.1562226840129%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title
Maxime KILT edited a comment on JENKINS-58315
Re: Allow to customize serverUrl while using rocketSend step
I don't think username/password are necessary when using a token for our incoming webhook. What are they for anyway?For info, today we use the [Slack plugin|https://github.com/jenkinsci/slack-plugin #security ] in a roundabout way for RocketChat but we cannot user the latest version:{code:java}slackSend(channel: 'jenkins',message: 'my message',baseUrl: 'https://myrocket.example.com/hooks/',teamDomain: 'myrocket',token: '0123456789'){code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1596.1562226900153%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title
Maxime KILT edited a comment on JENKINS-58315
Re: Allow to customize serverUrl while using rocketSend step
I don't think username/password are necessary when using a token for our incoming webhook. What are they for anyway?For info, today we use the [Slack plugin|https://github.com/jenkinsci/slack-plugin] in a roundabout way for RocketChat but we cannot user use the latest version:{code:java}slackSend(channel: 'jenkins',message: 'my message',baseUrl: 'https://myrocket.example.com/hooks/',teamDomain: 'myrocket',token: '0123456789'){code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1597.1562226900166%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title
Maxime KILT edited a comment on JENKINS-58315
Re: Allow to customize serverUrl while using rocketSend step
I don't think username/password are necessary when using a token for our incoming webhook. What are they for anyway?For info, today we use the [Slack plugin|https://github.com/jenkinsci/slack-plugin] v2.17 (latest version not working) in a roundabout way for RocketChat but we cannot use the latest version :{code:java}slackSend(channel: 'jenkins',message: 'my message',baseUrl: 'https://myrocket.example.com/hooks/',teamDomain: 'myrocket',token: '0123456789'){code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1600.1562226960099%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58338) 2 Security vulnerability in Delivery pipeline View: 1.3.2
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-58338 2 Security vulnerability in Delivery pipeline View: 1.3.2 Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2019-07-04 08:11 Environment: Jenkins: 2.150.1 Delivery pipeline View: 1.3.2 Priority: Blocker Reporter: Govind Sureka We are using plugin 'Delivery Pipeline View' on Jenkins to view the jobs in downstream section. The client evaluated the plugin for the vulnerability issues and found 2 severe vulnerabilities. Want to understand could you be able to fix those vulnerabilities then we can use this in Production environment. Quick action appreciated. Add Comment
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Søren Friis updated an issue Jenkins / JENKINS-56773 High master CPU usage introduced by Blue Ocean 1.14.0 Change By: Søren Friis Attachment: computers_GET.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198417.1553679453000.1611.1562228340443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50561) Add @Symbol to "throttle builds" job properties
Title: Message Title Reinhold Füreder commented on JENKINS-50561 Re: Add @Symbol to "throttle builds" job properties (I can confirm that it is not working and just silently ignored ) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189630.1522823307000.1621.1562228460436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Algimantas Lazauskas commented on JENKINS-58311 Re: NotSerializableException when uploading apk with appcenter-plugin Same problem (Master + Slaves, all Mac ). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200419.1562139986000.1624.1562228460488%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57338) Lockable resource didn't work, if two jobs acquires lock at same time
Title: Message Title ethorsa commented on JENKINS-57338 Re: Lockable resource didn't work, if two jobs acquires lock at same time Can you check the log of the first build for a double release of the Lock? I recently had a build where the lock was released twice: At the end of the stage (as expected) and once more at the end of the pipeline. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199113.1557130181000.1626.1562228460533%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Søren Friis commented on JENKINS-56773 Re: High master CPU usage introduced by Blue Ocean 1.14.0 We are still seeing a very high amount of CPU time spend servicing the following endpoint on Blue Ocean 1.17.0 /blue/rest/organizations/jenkins/computers/ computers_GET.png I tried blocking the endpoint in my browser, and everything seemed to function normally on Blue Ocean pages. Can the polling of this endpoint be disabled or reduced? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198417.1553679453000.1630.1562228580271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57732) 安装插件报错
Title: Message Title Richard Bywater commented on JENKINS-57732 Re: 安装插件报错 Hi - are you able to please translate the subject to English and also provide some more details about the issue you are facing? Thanks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199675.1559117775000.1637.1562228940278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Richard Bywater commented on JENKINS-58324 Re: HTML report do not show from Jenkins page (html error 404 on page js file) Hi Ante Kevrić - are you able to confirm what the "file structure" image is supposed to be showing (i.e. the contents of the ZIP file or the build directory on the Jenkins server as the files showing as 404 in the browser console view don't appear in the "file structure" image. Also sharing your config would be useful for replication purposes. Thanks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200432.1562163785000.1642.1562229600429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Enrique Fernández-Polo created an issue Jenkins / JENKINS-58339 Support new types of credentials Issue Type: Improvement Assignee: Enrique Fernández-Polo Components: aws-secrets-manager-credentials-provider-plugin Created: 2019-07-04 08:44 Priority: Minor Reporter: Enrique Fernández-Polo Hello! I've created a [fork|https://github.com/Quaiks/aws-secrets-manager-credentials-provider-plugin] and I am adding new type of credentials. The principle is simple: add a tag in AWS with the secret type and store a JSON as value. I am looking for some feedback of the implementation. Right now only happy paths are implemented but I would like to know if I am following the proper path. Thanks in advance! Add Comment
[JIRA] (JENKINS-58340) docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0
Title: Message Title Alon Bar-Lev created an issue Jenkins / JENKINS-58340 docker-plugin-1.1.6 docker cloud does not work with >=ssh-slaves-plugin-1.30.0 Issue Type: Improvement Assignee: Nicolas De Loof Components: docker-plugin, ssh-slaves-plugin Created: 2019-07-04 08:44 Environment: Regression: SSH Slaves 1.30.0 Good:: SSH Slaves 1.29.4 Docker plugin: 1.1.6 Labels: regression Priority: Major Reporter: Alon Bar-Lev When using docker plugin With docker cloud With Docker agent template of connect method "Connect with SSH" and with "Inject SSH key". Everything is working nicely with SSH Slaves 1.29.4 and breaks in SSH Slaves 1.30.0. The docker slave is running but the jenkins is not succeeding in opening the SSH channel. Add Comment
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Enrique Fernández-Polo updated an issue Jenkins / JENKINS-58339 Support new types of credentials Change By: Enrique Fernández-Polo Hello!I've created a [fork|[https://github.com/Quaiks/aws-secrets-manager-credentials-provider-plugin]] and I am adding new type of credentials.The principle is simple: add a tag in AWS with the secret type and store a JSON as value. I am looking for some feedback of the implementation. Right now only happy paths are implemented but I would like to know if I am following the proper path. Thanks in advance! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.1648.1562229960067%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step ok, I like the idea, i think could be easily added. But already struggeling with issues on the latest RocketChat API and will take some time to get it fixed Nevertheless any PR with this feature is welcome 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1650.1562230020143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57383) Issue when testing proxy
Title: Message Title Tobias Honacker commented on JENKINS-57383 Re: Issue when testing proxy We are also facing this issue. We downgrade from 2.183 to 2.165. It's working again. This problem should be fixed asap 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.1652.1562230500202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Peter Oost commented on JENKINS-58311 Re: NotSerializableException when uploading apk with appcenter-plugin Mez Pahlan Thanks for taking the time to look at this. This setup has a master and multiple slaves, all running Linux (there is also a Mac OS slave but that's not building this project). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200419.1562139986000.1661.1562230800434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57385) Found "HTTP ERROR 404" in html publish report after running my newman scripts
Title: Message Title Richard Bywater commented on JENKINS-57385 Re: Found "HTTP ERROR 404" in html publish report after running my newman scripts Are you able to confirm there is an index.html in the APIs\newman directory? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199167.155739919.1665.1562230860182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54706) Drop support for themes
Title: Message Title Tommy Tynjä updated JENKINS-54706 Jenkins / JENKINS-54706 Drop support for themes Change By: Tommy Tynjä Status: Open Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195506.1542660759000.1670.1562231280173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58332) Fix broken promotion duration display
Title: Message Title Tommy Tynjä updated JENKINS-58332 Jenkins / JENKINS-58332 Fix broken promotion duration display Change By: Tommy Tynjä Status: Open Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200444.156221941.1671.1562231280279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Nicholas Brown commented on JENKINS-53767 Re: Offer plugin management tooling This might help address the following ansible jenkin plugin management problem: https://github.com/ansible/ansible/issues/24864 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194275.1537882941000.1674.1562231341321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Component/s: _unsorted Component/s: core 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198931.1556177657000.1690.1562231820062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Mez Pahlan commented on JENKINS-58311 Re: NotSerializableException when uploading apk with appcenter-plugin It seems to be something with the fact that a master slave setup is being used. This is definitely a hug in the plugin. I need to find a way to pass the details of the build from the master to the slave. Specifically Retrofit. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200419.1562139986000.1693.1562232720362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-07-04 09:31 Priority: Minor Reporter: Ramon Leon The plugin is writing some markdown plugins. So far, it's up to the developer to identify what pieces of data may have special characters and escape them with custom methods. There are a lot of texts not being escaped, for example: paths of files or directories with underscores labels with underscores etc This ticket is to add a markdown library to write this type of files giving the responsibility of escaping the text to the library, therefore doing a best formatting. Add Comment
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Change By: Ramon Leon Issue Type: Improvement Bug 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200454.1562232715000.1702.1562232780667%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Change By: Ramon Leon The plugin is writing some markdown plugins. So far, it's up to the developer to identify what pieces of data may have special characters and escape them with custom methods. There are a lot of texts not being escaped, for example: * paths of files or directories with underscores * labels with underscores * etcThis ticket is to add a markdown library to write this type of files giving the responsibility of escaping the text to the library, therefore doing a best better formatting. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200454.1562232715000.1697.1562232780604%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-58311 NotSerializableException when uploading apk with appcenter-plugin Change By: Mez Pahlan Priority: Minor Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200419.1562139986000.1700.1562232780643%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Change By: Ramon Leon The plugin is writing some markdown plugins. So far, it's up to the developer to identify what pieces of data may have special characters and escape them with custom methods. There are a lot of texts not being escaped, for example: * paths of files or directories with underscores * labels with underscores * etcThis ticket is to add a markdown library to write this type of files giving the responsibility of escaping the text to the library, therefore doing a better formatting. I consider it a bug because currently there is a lot of unescaped texts that should be escaped. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200454.1562232715000.1704.1562232840133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title Karl Wirth commented on JENKINS-54475 Re: p4sync hangs at "p4 sync -f -q" Hi Bing Shiao - Great that you found a workaround. If you would like to investigate further please let me know. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195241.1541458128000.1706.1562232961103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title Karl Wirth closed an issue as Cannot Reproduce Workaround found. Jenkins / JENKINS-54475 p4sync hangs at "p4 sync -f -q" Change By: Karl Wirth Status: Open Closed Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195241.1541458128000.1708.1562233020538%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Tommy Tynjä commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors Delivery Pipeline plugin fix released in delivery pipeline plugin 1.4.0. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174214.1473344854000.1711.1562233140254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57451) Upgrade checkstyle to avoid external DTD access
Title: Message Title Tommy Tynjä updated JENKINS-57451 Released in Delivery Pipeline plugin 1.4.0. Jenkins / JENKINS-57451 Upgrade checkstyle to avoid external DTD access Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199264.155782373.1723.1562233200715%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57450) Update delivery pipeline plugin to support JDK11 build environment (current LTS Java version)
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-57450 Update delivery pipeline plugin to support JDK11 build environment (current LTS Java version) Change By: Tommy Tynjä Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199263.1557823339000.1721.1562233200691%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54706) Drop support for themes
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-54706 Drop support for themes Change By: Tommy Tynjä Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195506.1542660759000.1717.1562233200623%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57451) Upgrade checkstyle to avoid external DTD access
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-57451 Upgrade checkstyle to avoid external DTD access Change By: Tommy Tynjä Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199264.155782373.1725.1562233200750%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54706) Drop support for themes
Title: Message Title Tommy Tynjä updated JENKINS-54706 Released in Delivery Pipeline plugin 1.4.0. Jenkins / JENKINS-54706 Drop support for themes Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195506.1542660759000.1716.1562233200478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57450) Update delivery pipeline plugin to support JDK11 build environment (current LTS Java version)
Title: Message Title Tommy Tynjä updated JENKINS-57450 Released in Delivery Pipeline plugin 1.4.0. Jenkins / JENKINS-57450 Update delivery pipeline plugin to support JDK11 build environment (current LTS Java version) Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199263.1557823339000.1719.1562233200669%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58332) Fix broken promotion duration display
Title: Message Title Tommy Tynjä updated JENKINS-58332 Released in Delivery Pipeline plugin 1.4.0. Jenkins / JENKINS-58332 Fix broken promotion duration display Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200444.156221941.1726.1562233260143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58332) Fix broken promotion duration display
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-58332 Fix broken promotion duration display Change By: Tommy Tynjä Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200444.156221941.1727.1562233260182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon assigned an issue to Unassigned Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Change By: Ramon Leon Assignee: Emilio Escobar 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200454.1562232715000.1729.1562234040134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58342) Activity and Branches views empty
Title: Message Title Romain Prévost created an issue Jenkins / JENKINS-58342 Activity and Branches views empty Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-07-04 09:57 Priority: Major Reporter: Romain Prévost When opening the Activity or Branches view on Blueocean I get the following exception and the views remain empty: blueocean-core-js.js:58316 Error fetching page TypeError: Cannot read property 'toLowerCase' of undefined at TimeHarmonizerUtil.getI18nTitle (blueocean-core-js.js:54653) at LiveStatusIndicator.render (blueocean-core-js.js:53961) at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (jenkins-design-language.js:49570) at ReactCompositeComponentWrapper._renderValidatedComponent (jenkins-design-language.js:49593) at ReactCompositeComponentWrapper.performInitialMount (jenkins-design-language.js:49133) at ReactCompositeComponentWrapper.mountComponent (jenkins-design-language.js:49029) at Object.mountComponent (jenkins-design-language.js:55369) at ReactCompositeComponentWrapper.performInitialMount (jenkins-design-language.js:49142) at ReactCompositeComponentWrapper.mountComponent (jenkins-design-language.js:49029) at Object.mountComponent (jenkins-design-language.js:55369) at ReactDOMComponent.mountChildren (jenkins-design-language.js:54331) at ReactDOMComponent._createInitialChildren (jenkins-design-language.js:50457) at ReactDOMComponent.mountComponent (jenkins-design-language.js:50276) at Object.mountComponent (jenkins-design-language.js:55369) at ReactDOMComponent.mountChildren (jenkins-design-language.js:54331) at ReactDOMComponent._createInitialChildren (jenkins-design-language.js:50457) at ReactDOMComponent.mountComponent (jenkins-design-languag
[JIRA] (JENKINS-58311) NotSerializableException when uploading apk with appcenter-plugin
Title: Message Title
Peter Oost commented on JENKINS-58311
Re: NotSerializableException when uploading apk with appcenter-plugin
It's not limited to the plugin though. I wrote a script that uses curl to access the AppCenter API directly and it receives the same exception during the second API call (uploading the apk). The script build step:
script {
def apiToken = ''
def ownerName = 'Me'
def appName = 'MyApp'
def apkFilename = 'myApp/build/outputs/apk/release/myApp-release-unsigned.apk'
echo "Preparing a release on AppCenter"
def rawResponse1 = sh(script: "curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-API-Token: $apiToken' 'https://api.appcenter.ms/v0.1/apps/$ownerName/$appName/release_uploads'", returnStdout: true)
echo "Raw response 1 : '${rawResponse1}'"
def slurper = new groovy.json.JsonSlurper()
def response1 = slurper.parseText("${rawResponse1}")
echo "Parsed response 1: ${response1}"
echo "Uploading apk file to AppCenter"
def rawResponse2 = sh(script: "curl -F 'ipa=@{apkFilename}' '${response1.upload_url}", returnStdout: true)
echo "Raw response 2 : '${rawResponse2}'"
echo "Release uploaded apk on AppCenter"
def rawResponse3 = sh(script: "curl -X PATCH --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-API-Token: ${apiToken}' -d '{ \"status\": \"committed\" }' 'https://api.appcenter.ms/v0.1/apps/$ownerName/$appName/release_uploads/${response1.upload_id}'", returnStdout: true)
echo "Raw response 3 : '${rawResponse3}'"
def response3 = slurper.parseText("${rawResponse3}")
echo "Distributing release to testers"
def rawResponse4 = sh(script: "curl -X PATCH --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-API-Token: ${apiToken}' -d '{ \"destination_name\": \"Internal test group\", \"release_notes\": \"Automated build\" }' 'https://api.appcenter.ms/${response3.release_url}'", returnStdout: true)
echo "Raw response 4 : '${rawResponse4}'"
}
and the exception:
an exception which occurred:
in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals
in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@42294e4a
in field com.cloudbees.groovy.cps.impl.CallEnv.caller
in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@6107f29
in field com.cloudbees.groovy.cps.Continuable.e
in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@4ce96240
in field org.jenkinsci.plugins.workflow.cps.CpsThread.program
in object org.jenkinsci.plugins.workflow.cps.CpsThread@37cfbea8
in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads
in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@55a85c71
in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@55a85c71
Caused: java.io.NotSerializableException: groovy.json.JsonSlurper
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926)
at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.j
[JIRA] (JENKINS-27512) Support icons for folders
Title: Message Title Roman Donchenko commented on JENKINS-27512 Re: Support icons for folders No, there should be at least two: StockFolderIcon (the default icon) MetadataActionFolderIcon 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161314.1426786361000.1735.1562235780158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58343) Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183
Title: Message Title Russell Currie created an issue Jenkins / JENKINS-58343 Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183 Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2019-07-04 10:36 Environment: OS: Ubuntu 16.04.6 LTS (amd64) JDK: openjdk-8-jre-headless:amd64 8u212-b03-0ubuntu1.16.04.1 Jenkins version 2.183 Jenkins installed from "https://pkg.jenkins.io/debian" repository Slave nodes launched by ssh Priority: Major Reporter: Russell Currie Problem occurs after upgrade to 2.183 from 2.182 and is not present in 2.182. Have a project configured with "Source Code Management"–>"Subversion" module. Project checks out a repository over https and has: Local module directory: svn Repository depth: infinity Check-out Strategy: Always check out a fresh copy Repository browser: (Auto) "Console Output" has the following message: Running as SYSTEM Building remotely on deadlock in workspace /scratch/jenkins-slave/workspace/CheckoutJob FATAL: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to deadlock at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:928) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaul
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Ante Kevrić updated an issue Jenkins / JENKINS-58324 HTML report do not show from Jenkins page (html error 404 on page js file) Change By: Ante Kevrić Attachment: Jenkins issue.zip 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200432.1562163785000.1741.1562236680172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Ante Kevrić commented on JENKINS-58324 Re: HTML report do not show from Jenkins page (html error 404 on page js file) Hi Richard Bywater - That structure is from downloaded ZIP. I added here zip file "Jenkins issue.zip" so you can see configuration, console output, and report. thx, A. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200432.1562163785000.1743.1562236920096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57553) High throughput causes ConcurrentModificationException
Title: Message Title
Thomas Hansen commented on JENKINS-57553
Re: High throughput causes ConcurrentModificationException
I am getting the same issue at the end of a piplene that uploads a large number of individual files to Azure Storage: hudson.remoting.ProxyException: java.util.ConcurrentModificationException {{ at java.util.ArrayList$Itr.checkForComodification(Unknown Source)}} {{ at java.util.ArrayList$Itr.next(Unknown Source)}} {{ at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:73)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)}} {{ at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)}} {{ at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88)}} {{ at com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.defaultWriteObject(SerializableConverter.java:214)}} {{ at com.thoughtworks.xstream.core.util.CustomObjectOutputStream.defaultWriteObject(CustomObjectOutputStream.java:80)}} {{ at java.util.Collections$SynchronizedCollection.writeObject(Unknown Source)}} {{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)}} {{ at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)}} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)}} {{ at java.lang.reflect.Method.invoke(Unknown Source)}} {{ at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)}} Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call java.util.Collections$SynchronizedList.writeObject() : null Debugging information message : Could not call java.util.Collections$SynchronizedList.writeObject() cause-exception : java.util.ConcurrentModificationException cause-message : null --- {{ at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)}} {{ at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)}} {{ at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)}} {{ at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)}} {{ at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88)}} {{ at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:81)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)}} {{ at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)}} {{ at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)}} {{ at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)}} {{ at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)}} Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize com.microsoftopentechnologies.windowsazurestorage.AzureBlobAction#indivi
[JIRA] (JENKINS-58280) NullPointerException from JIRA site section, when modifying or saving a job
Title: Message Title
Egor Voronyansky updated an issue
Jenkins / JENKINS-58280
NullPointerException from JIRA site section, when modifying or saving a job
Change By:
Egor Voronyansky
Hi all, after a Jenkins Update (I don't remember the exact version, but I still found this issue using Jenkins 2.176.1 CI BlueOcean version, and Jira plugin 3.0.8), everytime I tried to modify or save a Job configuration, this error occursA problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack trace {code} java.lang.NullPointerException at hudson.plugins.jira.JiraSite.getName(JiraSite.java:504) at hudson.plugins.jira.JiraProjectProperty$DescriptorImpl.doFillSiteNameItems(JiraProjectProperty.java:111) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(Plugi
[JIRA] (JENKINS-58280) NullPointerException from JIRA site section, when modifying or saving a job
Title: Message Title
Egor Voronyansky updated an issue
Jenkins / JENKINS-58280
NullPointerException from JIRA site section, when modifying or saving a job
Change By:
Egor Voronyansky
Hi all, after a Jenkins Update (I don't remember the exact version, but I still found this issue using Jenkins 2.176.1 CI BlueOcean version, and Jira plugin 3.0.8), everytime I tried to modify or save a Job configuration, this error occursA problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack trace{code}java.lang.NullPointerException at hudson.plugins.jira.JiraSite.getName(JiraSite.java:504) at hudson.plugins.jira.JiraProjectProperty$DescriptorImpl.doFillSiteNameItems(JiraProjectProperty.java:111) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginS
[JIRA] (JENKINS-56243) Jenkins GUI is slow -removing cookie fixes it (temporarily)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-56243 Jenkins GUI is slow -removing cookie fixes it (temporarily) Change By: Daniel Beck Labels: lts-candidate user-experience 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197810.1550821517000.1790.1562238847606%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58326) UI Test Capture Plugin is not publishing results on jenkins dashboard
Title: Message Title Anvesh Thada assigned an issue to Victor Bathke Hey Victor, Can you please look into this ticket. Cheers, Jenkins / JENKINS-58326 UI Test Capture Plugin is not publishing results on jenkins dashboard Change By: Anvesh Thada Assignee: Victor Bathke 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200435.1562170578000.1798.1562239560652%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58343) Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-58343 Subversion Module giving "FATAL: Jenkins.instance is missing" on upgrade to 2.183 Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200456.1562236576000.1802.1562242080309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Peter Niederlag commented on JENKINS-44869 Re: Activity tabs Run id column should expand to fit value does anybody have a solution yet? I'd like to see the RUN column to take up more space (1.5x or 2x) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182935.1497419598000.1804.1562242201910%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding commented on JENKINS-58339 Re: Support new types of credentials Hi Enrique, This is a feature I’ve been musing on for a little while. As I see it, there’s a few different solutions possible. I initially developed the plugin with just the Secret Text credential Type for the following reasons: It was easier to build for an initial release (obviously). Travis CI, Circle CI, and some other CI products only have a notion of environment variables and encrypted environment variables (equivalent to Jenkins Secret Text credentials). They’ve been able to get along fine with these, and haven’t needed to add extra credential types, which suggests that maybe Jenkins is over-complicating credentials (when Secret Text alone would do the job). (Of course, if you really need an SSH key, it’s still possible in Travis/Circle - you can base64-encode the SSH key and store it in an encrypted env var.) It makes storage and retrieval of credentials a lot easier if you know that a credential can only be a simple arbitrary string (or byte array). It enables a secret to be saved once in AWS and then shared across any consuming application - not just Jenkins. Point 4 is probably the strongest reason not to support multiple credential types in the AWS Secrets Manager provider. If we invent a Jenkins-proprietary schema for complex credential types eg SSH key (username, key, passphrase (optional)), only Jenkins will understand it, and we’ll have to either duplicate that credential for our other applications, or update them all to understand the Jenkins credential schema. However... this is a tricky architectural problem. There’s probably not a single perfect answer to it. I’d be interested to hear other views on this Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:
[JIRA] (JENKINS-31209) Make the length of the build description display user settable
Title: Message Title Marty S commented on JENKINS-31209 Re: Make the length of the build description display user settable I just ran into this myself. Also I think that HTML code such as links counts towards the maximum, which is annoying since I like to put quick-links into the description. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165871.1445998325000.1820.1562247300305%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart FABRIZIO MANFREDIRaihaan Shouhell I know this is OSS and there are is not SLA. Still could you tell me if I and when I can expect any assistance from you. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1828.1562247360241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart [~thoulen][~raihaan] I know this is OSS and there are is not SLA. Still could you tell me if I and when I can expect any assistance from you . ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1830.1562247420130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Rick Clephas created an issue Jenkins / JENKINS-58344 User with only project level create credentials permission can't create credentials Issue Type: Bug Assignee: Oleg Nenashev Components: core, credentials-plugin, role-strategy-plugin Created: 2019-07-04 13:37 Environment: Jenkins ver. 2.176.1 Role Strategy Plugin ver. 2.12 Credentials Plugin ver. 2.2.0 Priority: Major Reporter: Rick Clephas User without the global create credentials permission can't create credentials for a project for which they do have the create credentials permissions. Configuration Role1 has global create, delete, manage domains, update and view credentials permissions Role2 has project create, delete, update and view credentials permissions Role2 has global view credentials permission **Issue Users with only Role2 can't create credentials for the job. The add button is greyed out and the add credentials options doesn't show in the side menu. Users who also have **Role1 can create global and job credentials. Users with only Role2 should be able to manage credentials for the job without the need of the global permission.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Maxime KILT commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step Yeah I think I will create a PR 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1835.1562248260096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Rick Clephas updated an issue Jenkins / JENKINS-58344 User with only project level create credentials permission can't create credentials Change By: Rick Clephas User without the global create credentials permission can't create credentials for a project for which they do have the create credentials permissions. h2. Configuration * Role1 has *global* create, delete, manage domains, update and view credentials permissions * Role2 has *project* create, delete, update and view credentials permissions * Role2 has *global* view credentials permissionh2. ** IssueUsers with only Role2 can't create credentials for the job. The add button is greyed out and the add credentials options doesn't show in the side menu.Users who also have **Role1 can create global and job credentials.Users with only Role2 should be able to manage credentials for the job without the need of the global permission. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.1837.1562248800312%40Atlassian.JIRA. For more op
[JIRA] (JENKINS-58345) Show trend graph on job summary, not full coverage results
Title: Message Title James Howe created an issue Jenkins / JENKINS-58345 Show trend graph on job summary, not full coverage results Issue Type: New Feature Assignee: Shenyu Zheng Components: code-coverage-api-plugin Created: 2019-07-04 13:59 Priority: Minor Reporter: James Howe To match most other plugins (warnings, test results, dependency-check, jacoco), the graph shown on the job summary should be the trend graph. Or, allow this to be configured. Add Comment This message was sent by Atlassia
[JIRA] (JENKINS-58346) Add exclude filter multibranch option
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-58346 Add exclude filter multibranch option Issue Type: Improvement Assignee: Unassigned Attachments: image-2019-07-04-15-16-06-142.png Components: p4-plugin Created: 2019-07-04 14:22 Environment: P4-Plugin 1.10.1 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth Method such as a tickbox to change the behavior of 'Include Filter' against multibranch definition to become an exclude filter. Example Usage Case Project includes the following branches and want to exclude *-Private from multi-branch definition: 1.2.3-Rel 1.2.3-QA 1.2.3-Dev 1.2.3-Private 1.2.4-Rel 1.2.4-QA 1.2.4-Dev 1.2.4-Private Workarounds at the moment would be: Use Perforce protections to hide *-Private from Jenkins user. Have multiple inclussionary expressions. For example '(.[1-9].*Rel)|(.[1-9].QA)|(.[1-9].*Dev)
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Fajran Rusadi commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository Tzach Yarimi to clarify, we had different multibranch pipeline job for different component. So what service does is create a new multibranch pipeline job when it detects a new component added to the repository. The new job will be configured to use the Jenkinsfile specific of that new component. If the job already exists, it will check if the branch is already registered otherwise it will update the job config to add a new branch and start the scanning process to make the branch job available. Once the branch job is available, the service will trigger the build of that. Unfortunately I could not share the code. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181165.1492753177000.1842.1562250242164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Maxime KILT commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step https://github.com/jenkinsci/rocketchatnotifier-plugin/pull/37 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.1957.1562252160373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-58347 Complete exclude function Issue Type: Task Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-04 15:07 Priority: Minor Reporter: Jeff Pearce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.1965.1562252880135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58348) Send email to dev list asking for UI feedback
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-58348 Send email to dev list asking for UI feedback Issue Type: Task Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-04 15:09 Priority: Minor Reporter: Jeff Pearce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200463.1562252946000.1967.1562253000121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58333) Implement Param Validation in Plugin Service
Title: Message Title Jeff Pearce commented on JENKINS-58333 Re: Implement Param Validation in Plugin Service Can you list the individual items that will be validated in the description? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200445.1562219609000.1969.1562253060140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58348) Send email to dev list asking for UI feedback
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-58348 Send email to dev list asking for UI feedback Change By: Jeff Pearce Labels: gsoc-2019 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200463.1562252946000.1971.1562253120323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-58347 Complete exclude function Change By: Jeff Pearce Labels: gsoc-2019 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.1973.1562253120360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Gavin Mogan commented on JENKINS-56773 Re: High master CPU usage introduced by Blue Ocean 1.14.0 disable the executor plugin, its no longer required 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198417.1553679453000.1975.1562253420244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Karl Wirth commented on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi both. I hit this invalid credentials when there was a typo in my credential ID. Can you please try the following simple code test to see if it works for you. Please replace 'JenkinsMaster' with the name of your Perforce credential ID and '//depot/Jam/...' with a small path in your depot:
def p4SyncLabel(String credential, String ws_name, String ws_view, String label, boolean append, boolean force){
echo "In function ..."
def ws = [$class: 'ManualWorkspaceImpl', name: ws_name, spec: [view: ws_view]]
def p4 = p4(credential: credential, workspace: ws)
p4.run('sync')
echo "... function end"
}
pipeline {
agent {
label 'master'
}
options {
timestamps()
}
stages {
stage('Test') {
steps{
echo 'Test'
script{
p4SyncLabel('JenkinsMaster', "jenkins_${NODE_NAME}_${JOB_BASE_NAME}_${EXECUTOR_NUMBER}",
"//depot/Jam/... //jenkins_${NODE_NAME}_${JOB_BASE_NAME}_${EXECUTOR_NUMBER}/...",
'head', true, false )
}
}
}
}
}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.1987.1562253840370%40Atlassian.JIRA.
For more options, visit https://groups.g
[JIRA] (JENKINS-58349) git-plugin ignore timeouts for advances behaviours
Title: Message Title Oren Shpigel created an issue Jenkins / JENKINS-58349 git-plugin ignore timeouts for advances behaviours Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-07-04 15:26 Environment: Jenkins 2.176.1 Git plugin 3.10.0 Labels: git plugin pipeline jenkins Priority: Minor Reporter: Oren Shpigel I have a pipeline projects that runs pipeline script from Git repo. The repo became big, and the clone operation times out after 10 minutes. I added "Advances checkout behaviours" and "Advances clone behaviours" with much bigger timeout, but it still times out after 10 minutes. hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128: stdout: stderr: remote: Enumerating objects: 6828, done. remote: Counting objects: 0% (1/6828) remote: Counting objects: 1% (69/6828) ... Receiving objects: 24% (5538/22691), 8.95 MiB | 14.00 KiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.S
[JIRA] (JENKINS-58350) Move the plugins used for test to /test/resources
Title: Message Title Kristin Whetstone created an issue Jenkins / JENKINS-58350 Move the plugins used for test to /test/resources Issue Type: Bug Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-04 15:30 Labels: plugin-manager Priority: Minor Reporter: Kristin Whetstone Going through the entire codebase this morning, I found that the plugins jpis that are used for tests are really stored in the /src/resources folder rather than the /test/resources folder. Just move the plugins for test and make sure the tests still work. Add Comment
[JIRA] (JENKINS-58348) Send email to dev list asking for UI feedback
Title: Message Title Jack Shen updated an issue Jenkins / JENKINS-58348 Send email to dev list asking for UI feedback Change By: Jack Shen Sprint: GSoC 2019. Coding Phase 2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200463.1562252946000.1996.1562256300253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58347) Complete exclude function
Title: Message Title Jack Shen updated an issue Jenkins / JENKINS-58347 Complete exclude function Change By: Jack Shen Sprint: GSoC 2019. Coding Phase 2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200462.1562252859000.1998.1562256300343%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58351) buildType is used incorrectly for windows builds
Title: Message Title Dennis Cappendijk created an issue Jenkins / JENKINS-58351 buildType is used incorrectly for windows builds Issue Type: Bug Assignee: Martin Weber Components: cmakebuilder-plugin Created: 2019-07-04 16:10 Environment: Windows + visual studio 2015 / Linux + unix makefiles Jenkins ver. 2.176.1 cmake builder plugin Version 2.6.2 Priority: Minor Reporter: Dennis Cappendijk I have created a Jenkins pipeline that covers both windows and linux. However it appears that cmakeBuild does not use buildType correctly for windows. For Linux is correctly adds -DCMAKE_BUILD_TYPE=Debug or Release in the configure step However for windows the CMAKE_BUILD_TYPE variable is ignored: 17:47:24Manually-specified variables were not used by the project: 17:47:24 17:47:24 CMAKE_BUILD_TYPE And subsequently in the --build step, the --config is unused. Resulting in a Debug-by-default build on windows. -config Debug or -config Release (depending on buildType should be added to the --build phase for windows (and CMAKE_BUILD_TYPE should not be used for windows) The current workaround to this is adding --config Debug/Release explicitly in the steps: steps: [[args: '--config Debug', withCmake: true]]
[JIRA] (JENKINS-38973) Multibranch-Pipeline Not Honoring Git Timeout
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38973 Multibranch-Pipeline Not Honoring Git Timeout Change By: Mark Waite Component/s: multi-branch-project-plugin (not Pipeline) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175390.1476389939000.2002.1562257560848%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58349) git-plugin ignore timeouts for advances behaviours
Title: Message Title Mark Waite updated JENKINS-58349 Jenkins / JENKINS-58349 git-plugin ignore timeouts for advances behaviours Change By: Mark Waite Status: Fixed but Unreleased Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200464.1562253998000.2030.1562257680813%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58349) git-plugin ignore timeouts for advances behaviours
Title: Message Title Mark Waite updated JENKINS-58349 Refer to the JENKINS-38973 workaround comment for this problem. Jenkins / JENKINS-58349 git-plugin ignore timeouts for advances behaviours Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200464.1562253998000.2028.1562257680663%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58228) CLI usage doesn't work if typo in args
Title: Message Title Natasha Stopa commented on JENKINS-58228 Re: CLI usage doesn't work if typo in args Fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/24 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200288.156159164.2031.1562261700048%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Chris Carr edited a comment on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi :). I ran the job, and it failed with the output below. I double checked the credentials name, and it was correct (and it's using the same credentials with a P4Sync call that has no problems). We're on version 1.9.6 of the Jenkins plugin, but plan on updating to 1.10.0 very shortly. {{ }} {{ Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on [Jenkins|https://jenkins-master.aws.bossalien.com/computer/(master)/] in /var/lib/jenkins/workspace/Project/Test_P4Jenkins[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] echo*17:37:36* Test[Pipeline] script[Pipeline] }} { {{ [Pipeline] echo*17:37:36* In function ...[Pipeline] p4[Pipeline] } }}{{ [Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timestamps[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentials }} {{ Finished: FAILURE }}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.2038.1562262420371%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Chris Carr commented on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi . I ran the job, and it failed with the output below. I double checked the credentials name, and it was correct (and it's using the same credentials with a P4Sync call that has no problems). We're on version 1.9.6 of the Jenkins plugin, but plan on updating to 1.10.0 very shortly. Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/Project/Test_P4Jenkins[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] echo*17:37:36* Test[Pipeline] script[Pipeline] {[Pipeline] echo*17:37:36* In function ...[Pipeline] p4[Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timestamps[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentials Finished: FAILURE
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.2034.1562262420294%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Chris Carr edited a comment on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi :). I ran the job, and it failed with the output below.I double checked the credentials name, and it was correct (and it's using the same credentials with a P4Sync call that has no problems). We're on version 1.9.6 of the Jenkins plugin, but plan on updating to 1.10.0 very shortly. --- Started by user ccarrRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/Project/Test_P4Jenkins[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] echo18:37:36 Test[Pipeline] script[Pipeline] { { [Pipeline] echo 18:37:36 In function ... [Pipeline] p4 [Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timestamps[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentialsFinished: FAILURE
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.2046.1562262600519%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Chris Carr edited a comment on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi :). I ran the job, and it failed with the output below.I double checked the credentials name, and it was correct (and it's using the same credentials with a P4Sync call that has no problems). We're on version 1.9.6 of the Jenkins plugin, but plan on updating to 1.10.0 very shortly. {{ }} {{ Started by user ccarr Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] nodeRunning nodeRunning on [ Jenkins |https://jenkins-master.aws.bossalien.com/computer/(master)/] in /var/lib/jenkins/workspace/Project/Test_P4Jenkins [Pipeline] { [Pipeline] timestamps [Pipeline] { [Pipeline] stage [Pipeline] { (Test) [Pipeline] echo *17 18 :37:36 * Test [Pipeline] script [Pipeline] }} { {{ [Pipeline] echo *17 18 :37:36 * In function ... [Pipeline] p4 [Pipeline] } }}{{ [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] } [Pipeline] // node [Pipeline] End of PipelineERROR PipelineERROR : P4: Task Exception: Invalid credentials }} {{ Finished: FAILURE }}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.2042.1562262600432%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Martin Weber resolved as Cannot Reproduce Jenkins / JENKINS-57502 Cmake arguments sometimes are added to path in parallel build Change By: Martin Weber Status: Open Resolved Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199365.1557999255000.2049.1562268660243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58350) Move the plugins used for test to /test/resources
Title: Message Title Natasha Stopa started work on JENKINS-58350 Change By: Natasha Stopa Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200465.1562254212000.2051.1562270100201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt updated JENKINS-58315 Jenkins / JENKINS-58315 Allow to customize serverUrl while using rocketSend step Change By: Martin Reinhardt Status: In Progress Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.2053.1562270340314%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58315) Allow to customize serverUrl while using rocketSend step
Title: Message Title Martin Reinhardt commented on JENKINS-58315 Re: Allow to customize serverUrl while using rocketSend step thanks for the PR 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200423.1562147249000.2055.1562270340339%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58351) buildType is used incorrectly for windows builds
Title: Message Title Martin Weber commented on JENKINS-58351 Re: buildType is used incorrectly for windows builds Cmake's evaluation of the CMAKE_BUILD_TYPE variable is not specific to the OS, it is specific to the buildscript generator. For the VS generator, apparently even the cmake guys could not find a way to generate build scripts for the VS build tool that pass the CMAKE_BUILD_TYPE-corresponding compiler/linker options to the compiler/linker. So users must take care to pass the '--config Debug' to the VS build tool themselve. As a workaround, you might want to try the nmake or nmake-jom generators. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200466.1562256626000.2057.1562270820132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58350) Move the plugins used for test to /test/resources
Title: Message Title Natasha Stopa updated JENKINS-58350 Jenkins / JENKINS-58350 Move the plugins used for test to /test/resources Change By: Natasha Stopa Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200465.1562254212000.2059.1562271006590%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58121) Use -- for long flags
Title: Message Title Natasha Stopa updated JENKINS-58121 Jenkins / JENKINS-58121 Use -- for long flags Change By: Natasha Stopa Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200166.1561046126000.2062.1562271060336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58104) Make Update Center Values Configurable
Title: Message Title Natasha Stopa updated JENKINS-58104 Jenkins / JENKINS-58104 Make Update Center Values Configurable Change By: Natasha Stopa Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200147.1560972534000.2063.1562271060359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
