[JIRA] (JENKINS-21322) Cleanup workspace when last build is >X days ago
Title: Message Title arthur m commented on JENKINS-21322 Re: Cleanup workspace when last build is >X days ago Hi, This ticket seems to implement exactly what I need, however I can't find how to turn it on in the Jenkins config. Is there anyone that could kindly point me to the proper page? Thanks, Arthur Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Daniel Qian commented on JENKINS-54872 Re: Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Cyrille Le Clerc I see, 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Cenk Tosun edited a comment on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) so it's not enough... I'll try to go into more detail:we are using pipeline jobs and in the job configuration we checkout the jenksfile Branch: * * /master or */releases/*Additial Behaviours: Don't trigger a build on commit notificationsIn the jenkinsfile we checkout several git reposBranch: * * /master or */releases/*Additial Behaviours:- useSubfolder- includePath- excludePath- UserExclusionwe are not using the multibranch pipeline plugini saw also your answer in https://issues.jenkins-ci.org/browse/JENKINS-50683 and the entry in the docu"In the event that Fast Remote Polling is detected as being not possible (branches to build contains wildcards, etc), polling will fallback to requiring a workspace."it looks like my problem is exactly related to this behavior by using:- wildcard branch names (changing to origin/master and origin/release/branchname is no problem)- an exclude message or path definition- an include region definition- an excluded user definitionand since we delete the workspace every night, we get this behavior.so due this facts it seems that atm frp is not possible for me. any idea how to handle this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54852) [MC 3.0] [Jenkins Plugin 5.6] In the Mobile center options specify aunthentication is not valid.
Title: Message Title feng jianzheng updated an issue Jenkins / JENKINS-54852 [MC 3.0] [Jenkins Plugin 5.6] In the Mobile center options specify aunthentication is not valid. Change By: feng jianzheng Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54853) [MC 3.0] [Jenkins Plugin 5.6] Use proxy settings cannot be disalbe.
Title: Message Title feng jianzheng updated an issue Jenkins / JENKINS-54853 [MC 3.0] [Jenkins Plugin 5.6] Use proxy settings cannot be disalbe. Change By: feng jianzheng Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title Mohamed Nazeer Mohamed Ibrahim commented on JENKINS-54445 Re: Publishing data to influxDb Thanks for reply!! If i want to add some more tag keys then what should i do? Any specific format for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Cenk Tosun commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) one detail more, we use also the additional behaviour : check out to specific local branch by using ** Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Cyrille Le Clerc commented on JENKINS-54872 Re: Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Thanks Daniel Qian for using the Pipeline Maven Integration. Your desire to rely on maven settings defined outside of the pipeline itself is definitively our best practice. So far, We have just considered to redefine default Maven (global) settings at the folder level (precisely at the AbstractFolder level) (here. If the config files can be redefined at the Pipeline (ie Item) level, then it would make sense to be able to define the Maven default settings at this level as well. A technical challenge I see supporting redefinition of default (global) Maven settings at the Pipeline level is that we would probably have to write a dedicated config screen. At the moment, our configuration block is a fragment intended to be included in the folder configuration file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer Open java jdk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54245 Jenkins windows installer should offer Open java jdk Change By: Oleg Nenashev Component/s: packaging Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer Open java jdk
Title: Message Title Oleg Nenashev commented on JENKINS-54245 Re: Jenkins windows installer should offer Open java jdk As a part of the JENKINS-52868 discussions in Platform SIG, it was decided that we want to exclude Java from the Windows installer at all. Alex Earl has a prototype for that AFAIK. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer Open java jdk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54245 Jenkins windows installer should offer Open java jdk Change By: Oleg Nenashev Issue Type: Task New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Oleg Nenashev commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free > Can we get this corrected? AFAICT https://github.com/jenkins-infra/crawler/blob/master/jdk.groovy#L27-L42 needs to be corrected. Somebody needs to propose a PR against this repo and then to test it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54305 Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Change By: Oleg Nenashev Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Oleg Nenashev assigned an issue to Devin Nusbaum Jenkins / JENKINS-54305 Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Change By: Oleg Nenashev Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Daniel Qian commented on JENKINS-54872 Re: Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Yes, I can use withMaven(mavenSettingsConfig:'...', globalMavenSettingsConfig: '...' but there are two problems: mavenSettingsConfig and globalMavenSettingsConfig use Config File ids, which is hard to maintain The most important thing is that makes the Jenkinsfile binds to a specific Jenkins configuration, which cannot be run everywhere. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title amol anil malokar commented on JENKINS-53888 Re: Batch step running on a node other than the master fails I change from 32 bit to 64 bit Java and Increased JVM heap size to 4GB seems to be working . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer Open java jdk
Title: Message Title Vishwadeep Bansal updated an issue Jenkins / JENKINS-54245 Jenkins windows installer should offer Open java jdk Change By: Vishwadeep Bansal Summary: Jenkins windows installer should offer zulu Open java jdk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Vishwadeep Bansal edited a comment on JENKINS-54245 Re: Jenkins windows installer should offer zulu java jdk hi [~oleg_nenashev]I am not sure about the linux version binaries, however, if we talk about Windows Installer then yes. Windows installer is integrated Oracle JDK, whereas oracle java free update is ending in Jan-19. Would that be possible if Jenkins Windows installer got any other OpenJDK integrated rather than oracle. Our enterprise is moving on Azulu Java, however if we you could use any other OpenJDK that is also fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title Shriram Datar commented on JENKINS-53888 Re: Batch step running on a node other than the master fails I am seeing the same issue with the latest Jenkins+ all up to date plugins. I am running only echo 1234 in the batch file. I have exact same logs as attached to this ticket Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title
Dominik Bartholdi commented on JENKINS-54872
Re: Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
the feature you request is not provided by the config-file-provider, but by the 'pipeline maven' plugin: https://plugins.jenkins.io/pipeline-maven beside this, I don't think this does make a lot of sense: If you expect this to be configured on each of the pipeline jobs, then you can also just do it inside the Jenkinsfile:
withMaven(mavenSettingsConfig: 'DEFAULT_MAVEN_SETTINGS', options: [artifactsPublisher(disabled: true)]) {
sh "mvn install"
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Vishwadeep Bansal commented on JENKINS-54245 Re: Jenkins windows installer should offer zulu java jdk hi Oleg Nenashev I am not sure about the linux version binaries, however, if we talk about Windows Installer then yes. Windows installer is integrated Oracle JDK, whereas oracle java free update is ending in Jan-19. Would that be possible if Jenkins Windows installer got any other OpenJDK integrated rather than oracle. Our enterprise is moving on Azulu Java, however if we could use any other OpenJDK that is also fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Daniel Qian updated an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Daniel Qian In a multibranch pipeline job, I can provide config files in that job and override global maven configuration.But in a pipeline job, I can to 't do those things. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Component/s: pipeline-maven-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title Aleksi Simell edited a comment on JENKINS-54445 Re: Publishing data to influxDb That is because with the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement " jenkins_data ", as documented. I will try to add those tags to all measurements once I find time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title Aleksi Simell commented on JENKINS-54445 Re: Publishing data to influxDb That is because with the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement jenkins_data as documented. I will try to add those tags to all measurements once I find time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title Mohamed Nazeer Mohamed Ibrahim commented on JENKINS-54445 Re: Publishing data to influxDb We have implemented the given solution but it seems the tags are not present in the databases. The influx version is : 1.5.4 jenkins Configuration is : step([$class: 'InfluxDbPublisher', customData: myDataMap, customDataMap: null, customPrefix: null, target: 'Jenkins Build Status', jenkinsEnvParameterTag: 'build_number=' + env.BUILD_NUMBER]) When we execute the below query in influxdb it shows nothing. SHOW TAG KEYS FROM "testcase_point" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54767) Global variables are overriding local variables
Title: Message Title Oleg Nenashev commented on JENKINS-54767 Re: Global variables are overriding local variables Which plugins do you use to define local and global variables? Please provide configuration screenshots if you are not sure. I would assume it is EnvInject, but it is not installed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Oleg Nenashev commented on JENKINS-54245 Re: Jenkins windows installer should offer zulu java jdk The issue was misreported to a wrong component in JIRA, it has been never triaged. Is it about the Windows installer? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54245 Jenkins windows installer should offer zulu java jdk Change By: Oleg Nenashev Assignee: Karl-Heinz Marbaise Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54245 Jenkins windows installer should offer zulu java jdk Change By: Oleg Nenashev Component/s: _unsorted Component/s: java-client-api Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54245) Jenkins windows installer should offer zulu java jdk
Title: Message Title Vishwadeep Bansal commented on JENKINS-54245 Re: Jenkins windows installer should offer zulu java jdk Hi Karl-Heinz Marbaise Please advise, when are we going to have the open JDK integrated in jenkins. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54873) jQuery v1.12.4 Library is outdated and vulnerable
Title: Message Title Vishwadeep Bansal created an issue Jenkins / JENKINS-54873 jQuery v1.12.4 Library is outdated and vulnerable Issue Type: Improvement Assignee: Unassigned Components: jquery-plugin Created: 2018-11-27 05:20 Environment: Production Priority: Major Reporter: Vishwadeep Bansal Hi, We are using jenkins version 2.138.2, during the penetration testing a following vulnerability has been identified. Could you please advise the the fix or provide the way update jquery library. Thanks. jQuery is a _javascript_ library used by the Focus application. jQuery contains a flaw that may allow DOM (Document Object Model) -based Cross-Site Scripting attacks, which exists because jQuery does not properly validate certain HTML tags being rendered. During the testing it is observed that jQuery v1.12.4 Library is used which is outdated and vulnerable. Below screenshot shows the jQuery Library version used in the application and related vulnerability. Recommendations: https://github.com/jquery/jquery-migrate/#readme Add
[JIRA] (JENKINS-54298) Jenkins crashes with Deadlock with EC2 Plugin
Title: Message Title Callum Pember edited a comment on JENKINS-54298 Re: Jenkins crashes with Deadlock with EC2 Plugin This happens to me too using the latest version of the plugin . I use the EC2 plugin pretty heavily with the 'Idle termination time' setting. I'm getting crashes every few days. I just installed the support core plugin and got a dump for when it happened today, if that would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54298) Jenkins crashes with Deadlock with EC2 Plugin
Title: Message Title Callum Pember edited a comment on JENKINS-54298 Re: Jenkins crashes with Deadlock with EC2 Plugin This happens to me too. I use the EC2 plugin pretty heavily with the 'Idle termination time' setting. I'm getting crashes every few days. I just installed the support core plugin and got a dump for when it happens happened today, if that would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54298) Jenkins crashes with Deadlock with EC2 Plugin
Title: Message Title Callum Pember commented on JENKINS-54298 Re: Jenkins crashes with Deadlock with EC2 Plugin This happens to me too. I use the EC2 plugin pretty heavily with the 'Idle termination time' setting. I'm getting crashes every few days. I just installed the support core plugin and got a dump for when it happens today, if that would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Mark Waite Summary: github multibranch builds fail to build with latest branch api and git plugin update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api and git plugin update
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api and git plugin update Change By: Mark Waite Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54287) Review student GSoC page for specific content
Title: Message Title Martin d'Anjou commented on JENKINS-54287 Re: Review student GSoC page for specific content See https://github.com/jenkins-infra/jenkins.io/pull/1905 Not finished yet. The big items that are still needed are: links to past year's presentations and slides to serve as example Coding style guidelines How to write blog posts on jenkinsio, how to write documentation for the gsoc 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44456) Provide a way to access a stage name from within the stage and its contents
Title: Message Title Jessie Ye commented on JENKINS-44456 Re: Provide a way to access a stage name from within the stage and its contents Is STAGE_NAME supported for parallel branches in scripted 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Daniel Qian created an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Issue Type: Bug Assignee: Dominik Bartholdi Attachments: multibranch-pipeline-1.png, multibranch-pipeline-2.png, pipeline-1.png Components: config-file-provider-plugin, pipeline Created: 2018-11-27 01:21 Priority: Minor Reporter: Daniel Qian In a multibranch pipeline job, I can provide config files in that job and override global maven configuration. But in a pipeline job, I can to those things. Add Comment
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: David van Laatum Attachment: image-2018-11-27-11-32-58-457.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title David van Laatum commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished I seem to have the same problem, so I created a job with the simple sleep 5 pipeline above and setup a cron job to check if the job has failed to finish recently then grab a thread dump and restart jenkins. I also noticed the test job starts taking longer and longer in the sleep step. < /td> Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: David van Laatum Attachment: image-2018-11-27-11-31-06-881.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-51568 Pipeline jobs hanging in Build Executor even if it is finished Change By: David van Laatum Attachment: thread_dump.html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api and git plugin update
Title: Message Title Jason Crow commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api and git plugin update Cool, works with just the API plugin reverted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api and git plugin update
Title: Message Title Mark Waite commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api and git plugin update It should be enough to revert branch API plugin 2.1.1. The changes between git plugin 3.9.0 and 3.9.1 added a requirement that POST must be used when checking the repository browser (SECURITY-810) and some minor automated testing changes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api and git plugin update
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api and git plugin update Change By: Mark Waite Summary: github multibranch builds fail to build with latest branch api and git plugin update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title
Josh McDonald edited a comment on JENKINS-41200
Re: Developer can see ANSI color in log file
Happy to see this! It's way more thorough than my experimental patch I never had the time to fix tests for :) All I did was stop stripping the codes, and bookend them with injected ` {code:java} ` {code} "tags" in the annotation stream.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Josh McDonald commented on JENKINS-41200 Re: Developer can see ANSI color in log file Happy to see this! It's way more thorough than my experimental patch I never had the time to fix tests for All I did was stop stripping the codes, and bookend them with injected `` and `->` "tags" in the annotation stream. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest git plugin update
Title: Message Title Jason Crow edited a comment on JENKINS-54864 Re: github multibranch builds fail to build with latest git plugin update Having the same problem PR's are detected but never built. I've reverted and PR's are building again. However there are error messages showing: *Dependency errors:*Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to restore the functionality provided by these plugins.Basic Branch Build Strategies Plugin version 1.1.1Branch API Plugin v2.0.21 is older than required. To fix, install v2.1.0 or later.Go to plugin managerConfigure which of these warnings are shown Warnings have been published for the following currently installed components.[Git plugin 3.9.0|http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin] [Server-side request forgery|https://jenkins.io/security/advisory/2018-06-04/#SECURITY-810] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest git plugin update
Title: Message Title Jason Crow commented on JENKINS-54864 Re: github multibranch builds fail to build with latest git plugin update Having the same problem PR's are detected but never built. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven
Title: Message Title Brad DeWindt created an issue Jenkins / JENKINS-54871 "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven Issue Type: Bug Assignee: Unassigned Attachments: maven configuration.png, sampleproject-output.txt Components: maven-plugin Created: 2018-11-26 23:23 Environment: OS: Server 2012R2 CPU: Intel Xeon E5-2690 2.59Ghz RAM: 22GB Jenkins running as: Domain service account with local administrator privileges Priority: Blocker Reporter: Brad DeWindt I created a Jenkins job using the maven plugin to run a gatling.io test, but it always fails with "java.lang.OutOfMemoryError: unable to create new native thread" (full output attached). I can run the maven job manually, from the workspace created by Jenkins, with "mvn gatling:test" and it runs without issue. The project I'm trying to run via Jenkins can be found at "https://github.com/gatling/gatling-maven-plugin-demo".
[JIRA] (JENKINS-54868) Display Organization/Project and Repository name(s) on the job details page
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54868 Display Organization/Project and Repository name(s) on the job details page Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Title: Message Title Sean Grider commented on JENKINS-13140 Re: Disconnected slaves come back online within a few minutes Going to have to agree with James Howe here. What workflow is Core targeting by even offering "Take this node offline" if it just comes back 30 seconds later? If the node has an issue causing all builds executed on it to fail, then I need to take it offline, so apparently this means I have to update its availability option and then take it offline? I could save a step by just updating the availability to use a schedule which is never available, which then prompts the question, why is there even a button to take offline in the first place if it doesn't really take it offline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54870) Allow "Publish cppCheck results" for failed builds
Title: Message Title Vlad Andone updated an issue Jenkins / JENKINS-54870 Allow "Publish cppCheck results" for failed builds Change By: Vlad Andone The CppCheck plugin does not execute post build step [ *Publish CppCheck results* ] if the build is already marked as failure. The plugin description sais: "_This plug-in is not invoked for failed builds, it is only called for stable or unstable builds (i.e., a build with failed tests)._"This really disables us to have our custom logic for deciding failure conditions * we do have many criteria and manage our own limit thresholds across more languages * for example we cannot see the CppChecks that need fixing, when the build failed also due to other reasons, like: unit tests, java/js compilation errors, java/js code checker errors, ...Can you please consider removing this restiction ? IMHO, It may be an advanced option that I need to tick on or off. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54870) Allow "Publish cppCheck results" for failed builds
Title: Message Title Vlad Andone created an issue Jenkins / JENKINS-54870 Allow "Publish cppCheck results" for failed builds Issue Type: Improvement Assignee: Marco Steffan Components: cppcheck-plugin Created: 2018-11-26 22:18 Environment: using cppcheck plugin version 1.24 & Jenkins version 2.138.3 Priority: Critical Reporter: Vlad Andone The CppCheck plugin does not execute post build step [*Publish CppCheck results*] if the build is already marked as failure. The plugin description sais: "This plug-in is not invoked for failed builds, it is only called for stable or unstable builds (i.e., a build with failed tests)." This really disables us to have our custom logic for deciding failure conditions we do have many criteria and manage our own limit thresholds across more languages for example we cannot see the CppChecks that need fixing, when the build failed also due to other reasons, like: unit tests, java/js compilation errors, java/js code checker errors, ... Can you please consider removing this restiction ? IMHO, It may be an advanced option that I need to tick on or off.
[JIRA] (JENKINS-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title
Glenn Herbert updated an issue
Jenkins / JENKINS-54869
Multibranch project truncates cloudbees folder workspace paths
Change By:
Glenn Herbert
With recent updates, the branch API plugin appears to truncate the cloudbees folder workspace paths. For example, we relocate the Jenkins workspace in the config.xml using{code:java} D:/builds/workspace/${ITEM_FULLNAME}{code} Our jobs are within multiple folders, ie ProjectBlue/Developer. This has always resulted in a build workspace at a well known location. For example, with a multibranch project *client_developer*, running a job from branch *APS-1137*, that location would be:{code:java}D:/builds/workspace/ProjectBlue/Developer/client_developer/APS-1137{code} However, with the latest update to branch api 2.1.1, we are seeing truncation of the path to:{code:java}D:/builds/workspace/eloper_client_developer_APS-1137{code} I see that a bunch of work lately has been dealing with slashes, percents, et.al. in workspace paths (JENKINS-38706,[JENKINS-30744,[JENKINS-39251]), but I cannot find one that exactly matches the issue described. The workspaces.txt file shows this truncation:{noformat}1: ProjectBlue/Developer/client_developer/9X_DotNetTool2: r_client_developer_9X_DotNetTool3: ProjectBlue/Developer/client_developer/APS-11374: eloper_client_developer_APS-11375: ProjectBlue/Developer/client_developer/APS-1145-Apr6: er_client_developer_APS-1145-Apr{noformat} Would I see that a bunch of work lately has been dealing with slashes, percents, et.al. in workspace paths (JENKINS-38706,[JENKINS-30744,JENKINS-39251), but I cannot find one that exactly matches the issue described.It would be nice to have some way to override or disable this truncation, restoring functionality of the full path, as this affects a great deal of downstream jobs that expect well known paths.
Add Comment
[JIRA] (JENKINS-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title
Glenn Herbert updated an issue
Jenkins / JENKINS-54869
Multibranch project truncates cloudbees folder workspace paths
Change By:
Glenn Herbert
With recent updates, the branch API plugin appears to truncate the cloudbees folder workspace paths. For example, we relocate the Jenkins workspace in the config.xml using{code:java} D:/builds/workspace/${ITEM_FULLNAME}{code} Our jobs are within multiple folders, ie ProjectBlue/Developer. This has always resulted in a build workspace at a well known location. For example, with a multibranch project *client_developer*, running a job from branch *APS-1137*, that location would be: {code:java}D:/builds/workspace/ProjectBlue/Developer/client_developer/APS-1137{code} However, with the latest update to branch api 2.1.1, we are seeing truncation of the path to:{code:java}D:/builds/workspace/eloper_client_developer_APS-1137{code}I see that a bunch of work lately has been dealing with slashes, percents, et.al. in workspace paths ( [ JENKINS-38706 |https://issues.jenkins-ci.org/browse/JENKINS-38706] ,[JENKINS-30744 |https://issues.jenkins-ci.org/browse/JENKINS-30744] ,[JENKINS-39251 |https://issues.jenkins-ci.org/browse/JENKINS-39251 ]), but I cannot find one that exactly matches the issue described.The workspaces.txt file shows this truncation: {noformat}1: ProjectBlue/Developer/client_developer/9X_DotNetTool2: r_client_developer_9X_DotNetTool3: ProjectBlue/Developer/client_developer/APS-11374: eloper_client_developer_APS-11375: ProjectBlue/Developer/client_developer/APS-1145-Apr6: er_client_developer_APS-1145-Apr{noformat} Would be nice to have some way to override or disable this truncation, restoring functionality of the full path, as this affects a great deal of downstream jobs that expect well known paths.
Add Comment
[JIRA] (JENKINS-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title
Glenn Herbert created an issue
Jenkins / JENKINS-54869
Multibranch project truncates cloudbees folder workspace paths
Issue Type:
Bug
Assignee:
Unassigned
Components:
branch-api-plugin
Created:
2018-11-26 21:51
Environment:
Windows Server 2008 R2 Enterprise, Jenkins 2.153, branch Api Plugin 2.1.1
Labels:
plugin workspace_corruption
Priority:
Major
Reporter:
Glenn Herbert
With recent updates, the branch API plugin appears to truncate the cloudbees folder workspace paths. For example, we relocate the Jenkins workspace in the config.xml using
D:/builds/workspace/${ITEM_FULLNAME}
Our jobs are within multiple folders, ie ProjectBlue/Developer. This has always resulted in a build workspace at a well known location. For example, with a multibranch project client_developer, running a job from branch APS-1137, that location would be:
D:/builds/workspace/ProjectBlue/Developer/client_developer/APS-1137
However, with the latest update to branch api
[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Ulli Hafner commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config And an additional note: the problem is not that the sax parser is a dependency of a plugin, somehow some plugin sets the property and should not do it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Ulli Hafner commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Yes these plugins are visible (static analysis utilities plugin and warning plugin). It is still not clear which plugins are actually causing the bug, so yes you can be affected even if you do not have these plugins installed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54833) Warnings Parser fails parsing log
Title: Message Title Ulli Hafner commented on JENKINS-54833 Re: Warnings Parser fails parsing log Hmm, I don’t think that generating a hash code to track new warnings is a security risk so I handle those files differently in these two separate post processing steps. Do you think it is necessary to prevent access to those files in any cases? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Is there a direct way to access the log on the agent? No. If you want to run warning parsers on the agent side, what you would rather want is a block-scoped step (perhaps via SimpleBuildWrapper) that uses a ConsoleLogFilter to track warnings as they are emitted, rather than parsing them later. (This would also be far more efficient in conjunction with cloud log storage.) But it is a significant rewrite to do that, and of course requires a different kind of project configuration as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin assigned an issue to Daniel Danan Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Eduard Karlin Assignee: Daniel MS Danan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin assigned an issue to Daniel MS Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Eduard Karlin Assignee: Eduard Karlin Daniel MS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin assigned an issue to Eduard Karlin Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Eduard Karlin Assignee: Daniel Danan Eduard Karlin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54868) Display Organization/Project and Repository name(s) on the job details page
Title: Message Title Tarun Gidwani created an issue Jenkins / JENKINS-54868 Display Organization/Project and Repository name(s) on the job details page Issue Type: Improvement Assignee: Mark Waite Attachments: issue-img2.jpg Components: git-plugin Created: 2018-11-26 20:21 Labels: plugin pipeline jenkins git plugins configuration Priority: Minor Reporter: Tarun Gidwani Currently when checking out multiple repositories or a single repository with submodules the Git plugin only displays the commit sha(s) and branch name(s) for each of the repositories being checked out on the job details page and as part of the Git Build Data. It would be useful to have the Organization/Project and Repository name(s) displayed alongside the commit sha(s) and branch name(s). This makes it easier to associate the changes to the repository.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title
Eduard Karlin commented on JENKINS-54632
Re: dsl job doesn't create a build step for Performance Center using Jenkins API
Hi Daniel, Somehow it's still not working for me. Now I can't even generate this build step on my old Jenkins Server. Maybe it's an issue wit pipeline name step? In the current code I see: 'pcModel' { 'pcServerName' 'cdlpfpcsvr04.es.ad.adp.com' 'almUserName' 'jenkinsACA' 'almPassword' 'adpaca' But you mentioned "pcBuild". Was it changed recently from "pcModel" to "pcBuild"? Maybe you also have some sample of groovy code which can be used to build this step? post build steps are generated with no issues: configure { project -> configure { project -> project / publishers << {'com.hp.application.automation.tools.results.RunResultRecorder'(plugin:"hp-application-automation-tools-plugin@4.0.1"){ '__resultsPublisherModel' { 'archiveTestResultsMode' 'PUBLISH_HTML_REPORT' } } } } publishers{ downstreamParameterized { trigger("Report for ${jobId}") { condition('SUCCESS') } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Jesse Glick commented on JENKINS-54640 Re: Workspace folders are not unique Lars-Magnus Skog yes the truncation is intentional, to limit the length of folder names, as some tools (especially, though not exclusively, on Windows) have trouble with long names. Josh Soref please open a separate bug report linked to JENKINS-2111, ideally with steps to reproduce from scratch if you can find them. Your stack trace suggests that Jenkins is trying to open a workspaces.txt which does not exist…immediately after verifying that it does exist. While I could certainly make this code more defensive in various ways, I would like to understand what is happening first. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Jesse Glick commented on JENKINS-41200 Re: Developer can see ANSI color in log file https://github.com/jenkinsci/ansicolor-plugin/pull/132#issuecomment-440937753 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46324) Support for ConsoleNote
Title: Message Title Jesse Glick commented on JENKINS-46324 Re: Support for ConsoleNote https://github.com/jenkinsci/ansicolor-plugin/pull/132#issuecomment-440937753 for this case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Darryl Pogue commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 After updating the ssh slaves plugin to 1.29.1, Jenkins will not connect to any of my build agents, and it complains about data stored in an old format: ConversionException: Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission Debugging information message : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Could not call com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource.readResolve() : anonymous is missing the Overall/RunScripts permission class : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource required-type : com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$UsersPrivateKeySource converter-type : hudson.util.RobustReflectionConverter path : /com.cloudbees.plugins.credentials.SystemCredentialsProvider/domainCredentialsMap/entry/java.util.concurrent.CopyOnWriteArrayList/com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey/privateKeySource line number : 21 --- Rebooting the Jenkins machine did not help, and neither has rebooting the build agent machines. 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
[JIRA] (JENKINS-54867) Define IANA Enterprise Number field as customizable
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-54867 Define IANA Enterprise Number field as customizable Change By: David Olorundare The RFC5424 layout - [https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout |https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout)]used in the log4j2.xml audit log file requires that the 'enterpriseNumber' field be set according to the standards. This issue needs to be further discussed to determined if the field should be remain a fixed value or be made customizable for other Jenkins distributions to be able to override it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54867) Define IANA Enterprise Number field as customizable
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-54867 Define IANA Enterprise Number field as customizable Change By: David Olorundare The [ RFC5424 layout ]( - [https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout |https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout )] used in the ` log4j2.xml ` audit log file requires that the ` ' enterpriseNumber ` ' field be set according to the standards. This issue needs to be further discussed to determined if the field should be remain a fixed value or be made customizable for other Jenkins distributions to be able to override it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54867) Define IANA Enterprise Number field as customizable
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-54867 Define IANA Enterprise Number field as customizable Change By: David Olorundare The [ ` RFC5424 ` layout]([https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout)] used in the `log4j2.xml` audit log file requires that the `enterpriseNumber` field be set according to the standards. This issue needs to be further discussed to determined if the field should be remain a fixed value or be made customizable for other Jenkins distributions to be able to override it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54867) Define IANA Enterprise Number field as customizable
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-54867 Define IANA Enterprise Number field as customizable Issue Type: Task Assignee: Unassigned Components: core Created: 2018-11-26 19:21 Priority: Minor Reporter: David Olorundare The [`RFC5424` layout](https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout) used in the `log4j2.xml` audit log file requires that the `enterpriseNumber` field be set according to the standards. This issue needs to be further discussed to determined if the field should be remain a fixed value or be made customizable for other Jenkins distributions to be able to override it. Add Comment
[JIRA] (JENKINS-54866) github_branch_source.GitHubSCMSource is ~0 width
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54866 github_branch_source.GitHubSCMSource is ~0 width Issue Type: Bug Assignee: Unassigned Attachments: image-2018-11-26-14-11-58-378.png, image-2018-11-26-14-14-53-644.png Components: github-branch-source-plugin Created: 2018-11-26 19:15 Environment: github-branch-source-plugin 2.4.1; Jenkins ver. 2.153; Chrome 70.0.3538.102 macOS Mojave Priority: Minor Reporter: Josh Soref Load http://jenkins/configure Scroll down to Global Pipeline Libraries Scroll to Source Code Management See: That tiny blob between GitHub and Credentials is "" nameref="radio-block-15"> "/descriptorByName/org.jenkinsci.plugins.github_branch_source.GitHubSCMSource/fillApiUriItems" name="_.apiUri" class="setting-input select" value="">GitHub
[JIRA] (JENKINS-54761) Downstream job not displaying in logs after upstream job is promoted
Title: Message Title Devin Nusbaum commented on JENKINS-54761 Re: Downstream job not displaying in logs after upstream job is promoted It looks like the message comes from Promotion$RunnerImpl#build. It's not obvious to me why the logs from running the promotions do not show up in the promotion log itself (are they available anywhere?!), and those log lines showing the BuildStep class name and instance are pretty terrible. It looks like the Jenkins core non-parameterized build trigger action is special-cased to print a hyperlink to the build, but we couldn't easily do the same for parameterized-trigger without introducing a circular dependency. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54783) Library additions to Global Variable Reference are not displayed formatted
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54783 Library additions to Global Variable Reference are not displayed formatted Change By: Vivek Pandey Labels: documentation Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54783) Library additions to Global Variable Reference are not displayed formatted
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54783 Library additions to Global Variable Reference are not displayed formatted Change By: Vivek Pandey Labels: documentation triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54763 Branch name disappear after plugin upgrade (>= 2.26) Change By: Vivek Pandey Labels: pipeline plugin triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title Vivek Pandey assigned an issue to Jesse Glick Jenkins / JENKINS-54763 Branch name disappear after plugin upgrade (>= 2.26) Change By: Vivek Pandey Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54764) builds fail when using timeout step with the Pipeline Basic Steps Plugin
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54764 builds fail when using timeout step with the Pipeline Basic Steps Plugin Change By: Vivek Pandey Labels: pipeline plugins triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54764) builds fail when using timeout step with the Pipeline Basic Steps Plugin
Title: Message Title Vivek Pandey assigned an issue to Jesse Glick Jenkins / JENKINS-54764 builds fail when using timeout step with the Pipeline Basic Steps Plugin Change By: Vivek Pandey Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54320) Move audit log plugin to jenkinsci organization
Title: Message Title Matt Sicker started work on JENKINS-54320 Change By: Matt Sicker 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54320) Move audit log plugin to jenkinsci organization
Title: Message Title Matt Sicker assigned an issue to David Olorundare Jenkins / JENKINS-54320 Move audit log plugin to jenkinsci organization Change By: Matt Sicker Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54636) Configure default audit logging output configuration
Title: Message Title Matt Sicker assigned an issue to David Olorundare Jenkins / JENKINS-54636 Configure default audit logging output configuration Change By: Matt Sicker Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54636) Configure default audit logging output configuration
Title: Message Title Matt Sicker started work on JENKINS-54636 Change By: Matt Sicker 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41100) Memory leak in web interface (Javascript)
Title: Message Title
Sven Appenrodt commented on JENKINS-41100
Re: Memory leak in web interface (_javascript_)
Maybe as fast workaround you can ignore the problem in IE and fix it for chrome and firefox by canging
if (Object.isUndefined(registry)) {
CACHE.push(element);
registry = Element.retrieve(element, 'prototype_event_registry', $H());
}
to
if (Object.isUndefined(registry)) {
if (!Prototype.Browser.IE) {
CACHE.push(element);
}
registry = Element.retrieve(element, 'prototype_event_registry', $H());
}
This will prevent the elements getting stored in the array for 'not IE' browser...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54761) Downstream job not displaying in logs after upstream job is promoted
Title: Message Title Dylan Dewhurst commented on JENKINS-54761 Re: Downstream job not displaying in logs after upstream job is promoted Devin Nusbaum The log is located here: http:///job/upstream-job/13/promotion/promtion%202/lastSuccessful/ This is the full console output: Started by user ddewhurst Building remotely on shared-ssh-agent (shared docker-cloud ssh docker) in workspace /home/jenkins/ad29aa2f/workspace/upstream-job Promoting upstream-job #13 [upstream-job] $ /bin/sh -xe /tmp/jenkins8487037222432658541.sh + echo promotion 2 promotion 2 build hudson.tasks.Shell@ce28f6 SUCCESS build hudson.plugins.parameterizedtrigger.BuildTrigger@62bd6e03 SUCCESS Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin I don't really see a way to restrict nodes with Authorize Project. Any notes on that or a post that describes that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest git plugin update
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest git plugin update Change By: Mark Waite Component/s: branch-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54453) Allow a user to validate the compatibility of the installed plugins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54453 Allow a user to validate the compatibility of the installed plugins Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54452) Allow a user to install their own set of plugins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54452 Allow a user to install their own set of plugins Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54449) Provide a Docker image based on alpine Linux
Title: Message Title Oleg Nenashev commented on JENKINS-54449 Re: Provide a Docker image based on alpine Linux Probably won't do. There is an ongoing discussion about abandoning the alpine images for Java 11. Anyway, it should be possible to just use an Alpine base image in the custom WAR Packager flow: https://github.com/jenkinsci/jenkinsfile-runner/tree/master/demo/cwp. Have you tried it Cosmin Cojocar ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54449) Provide a Docker image based on alpine Linux
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54449 Provide a Docker image based on alpine Linux Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54452) Allow a user to install their own set of plugins
Title: Message Title Oleg Nenashev commented on JENKINS-54452 Re: Allow a user to install their own set of plugins Cosmin Cojocar from your PoV, what does need to happen on the Jenkinsfile Runner side? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54425) "update plugin to a version created with a newer harness" warnings in the default STDOUT
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54425 "update plugin to a version created with a newer harness" warnings in the default STDOUT Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
