[JIRA] (JENKINS-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Thomas Vuillaume edited a comment on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished I'm sharing my Pipeline file so that we can move on (and maybe found a root cause). Anyway, this is pretty strange because we have 2 different Jenkins here. Both of them are on 2.138.2, both of them use Pipeline Build 1.5.8. Both of them use a pipeline to build, but not the same pipeline. Only one faces the issue (the one which I published uses the pipeline I added 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Thomas Vuillaume edited a comment on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished I'm sharing my Pipeline file so that we can move on (and maybe found a root cause). Anyway, this is pretty strange because we have 2 different Jenkins here. Both of them are on 2.138.2, both of them use Pipeline Build 1.5.8. Both of them use a pipeline to build, but not the same pipeline. Only one face faces the issue (the one which I published 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Thomas Vuillaume commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished I'm sharing my Pipeline file so that we can move on (and maybe found a root cause). Anyway, this is pretty strange because we have 2 different Jenkins here. Both of them are on 2.138.2, both of them use Pipeline Build 1.5.8. Both of them use a pipeline to build, but not the same pipeline. Only one face the issue (the one which I published 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Thomas Vuillaume updated an issue Jenkins / JENKINS-54678 Logs are lost in Multibranch Pipleline after the build has finished Change By: Thomas Vuillaume Attachment: standardModulePipeline.groovy 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-54596) can't parse argument number: changelog.url
Title: Message Title 凌瑞 涂 commented on JENKINS-54596 Re: can't parse argument number: changelog.url I remove a Chinese Localization plugin after，just fine who can help me~ 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-54318) Jenkins Upgrade Now deletes new .war at restart
Title: Message Title Rene Affourtit edited a comment on JENKINS-54318 Re: Jenkins Upgrade Now deletes new .war at restart When updating from 2.15*1* to 2. 153 152 I intentionally doubleclicked. The symptoms are the same, so Ill try to reproduce with 1.53 to a higher version once that becomes available. [edit] would have sworn I saw 2.153, now it says 2.152. updated to match. 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-54318) Jenkins Upgrade Now deletes new .war at restart
Title: Message Title Rene Affourtit commented on JENKINS-54318 Re: Jenkins Upgrade Now deletes new .war at restart When updating from 2.15*1* to 2.153 I intentionally doubleclicked. The symptoms are the same, so Ill try to reproduce with 1.53 to a higher version once that becomes available. 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-54318) Jenkins Upgrade Now deletes new .war at restart
Title: Message Title Rene Affourtit updated an issue Jenkins / JENKINS-54318 Jenkins Upgrade Now deletes new .war at restart Change By: Rene Affourtit Attachment: DoubleClick.err 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-44094) Hide specific steps in build view
Title: Message Title
Anton Yurchenko commented on JENKINS-44094
Re: Hide specific steps in build view
I have an example of situations when hiding stages are required. Multi-branch pipeline, when push on different branch should create a different slave node in different network segment. In order to filter specific use case we are using WHEN condition. In such case, there are lots of 'pseudo' stages like "Branch: dev/master", "Branch: dev", "Env: development", "Env: production", "Branch: master". Such drill down also breaks the console output as two stages running in UI (for example: Branch: dev and Spawn Slave)
stage("Branch: dev/master"){
parallel {
stage("Env: development") {
when {
allOf {
branch 'dev'
environment name: 'CHANGE_TARGET', value: ''
}
}
stages {
stage("Branch: dev"){
agent {label "development-slave"}
stages {
stage("Spawn Slave") {
steps {
sh 'command'
}
post {
failure {
sh 'command'
}
aborted {
sh 'command'
}
}
}
stage("Base Image") {
steps {
sh 'command'
}
post {
aborted {
sh 'command'
}
failure {
sh 'command'
}
}
}
stage("Dev Image") {
steps {
sh 'command'
}
post {
aborted {
sh 'command'
}
failure {
sh 'command'
}
}
}
stage("Notify Team"){
agent {label "master"}
steps {
sh 'command'
}
}
stage('Deploy QA') {
steps {
sh 'command'
}
post {
success {
sh 'command'
}
failure {
sh 'command'
}
aborted {
sh 'command'
}
always {
sh 'command'
}
}
}
}
}
}
}
stage("Env: production") {
when {
allOf {
branch 'master'
environment name: 'CHANGE_TARGET', value: ''
}
}
stages {
stage("Branch: master"){
agent {label "production-slave"}
stages {
stage("Spawn Slave") {
steps {
sh 'command'
}
post {
failure {
sh 'command'
}
aborted {
sh 'command'
}
}
}
stage("Base Image") {
steps {
sh 'command'
}
post {
aborted {
sh 'command'
}
failure {
sh 'command'
}
}
}
stage("Prod Image") {
steps {
sh 'command'
}
post {
success {
[JIRA] (JENKINS-54851) Parallel Integration Testing
Title: Message Title
Mahesh Subramanian created an issue
Jenkins / JENKINS-54851
Parallel Integration Testing
Issue Type:
Task
Assignee:
Unassigned
Components:
parallel-test-executor-plugin
Created:
2018-11-26 06:25
Environment:
I was just trying to setup Parallel integration Testing for browser. I tried to execute the below script. But it hangs. Could you please let me know what could be done here? node { parallel chrome: { runTests("Chrome") }, firefox: { runTests("Firefox") }, safari: { runTests("Safari") } } def runTests(browser) { node { sh 'rm -rf *' unstash 'everything' sh 'npm run test-single-run -- -- browsers $(browser)' } }
Priority:
Minor
Reporter:
Mahesh Subramanian
Add Comment
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Jason Waldrip commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Same issue. Causing a lot of developer frustration on the team. 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-4828) EC2 provides instance info and a way to use it in scripts run on the master to control the slave.
Title: Message Title Owen Mehegan closed an issue as Won't Do Jenkins / JENKINS-4828 EC2 provides instance info and a way to use it in scripts run on the master to control the slave. Change By: Owen Mehegan Status: Open Closed Resolution: Won't Do 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-53913) Customizable graceful shutdown timeout in vSphere Could plugin
Title: Message Title Rudolf-Walter Kiss-Szakacs updated JENKINS-53913 Jenkins / JENKINS-53913 Customizable graceful shutdown timeout in vSphere Could plugin Change By: Rudolf-Walter Kiss-Szakacs Status: In Review Resolved Resolution: Done 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 assigned an issue to Martin d'Anjou Jenkins / JENKINS-54287 Review student GSoC page for specific content Change By: Martin d'Anjou Assignee: Martin d'Anjou 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 started work on JENKINS-54287 Change By: Martin d'Anjou 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-52397) Org Scan blows up when repository has no tags
Title: Message Title Stephen Connolly commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags https://github.com/jenkinsci/github-branch-source-plugin/commit/3079fd6d0609bf0a6387729c0da756ed08abfabc was merged... just waiting on rsandell to cut a release... or you could take the snapshot build from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgithub-branch-source-plugin/detail/master/82/artifacts 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-53858) Deadlock on EC2 resources
Title: Message Title Ashish Sanagar commented on JENKINS-53858 Re: Deadlock on EC2 resources How to get 1.42 release? its not available on jenkins plugin manager updates. and dont see available for download 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-54850) ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant
Title: Message Title
Chris Hunt updated an issue
Jenkins / JENKINS-54850
ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant
Change By:
Chris Hunt
As described in [{{ParameterizedJobMixIn.scheduleBuild2}}|https://javadoc.jenkins.io/jenkins/model/ParameterizedJobMixIn.html#scheduleBuild2-hudson.model.Job-int-hudson.model.Action...-], passing {{-1}} as the {{quietPeriod}} causes the method to use the default quiet period configured for the job. We If plugin authors have warnings or style checkers configured to reject "magic constants", then it is necessary to give this value a name and use it in the call to {{scheduleBuild2}}. For convenience of use, we should expose a static constant e.g. {{USE_DEFAULT_QUIET_PERIOD}} with the value {{-1}} so each plugin authors do author does not have to keep add include such a named value for it constant in their plugins to avoid warnings about "magic numbers" 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54850) ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant
Title: Message Title
Chris Hunt updated an issue
Jenkins / JENKINS-54850
ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant
Change By:
Chris Hunt
As described in [{{ParameterizedJobMixIn.scheduleBuild2}}|https://javadoc.jenkins.io/jenkins/model/ParameterizedJobMixIn.html#scheduleBuild2-hudson.model.Job-int-hudson.model.Action...-], passing {{-1}} as the {{quietPeriod}} causes the method to use the default quiet period configured for the job . We should expose a static constant e.g. {{USE_DEFAULT_QUIET_PERIOD}} so plugin authors do not have to keep a named value for it in their plugins to avoid warnings about "magic numbers".
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-54850) ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant
Title: Message Title Chris Hunt created an issue Jenkins / JENKINS-54850 ParameterizedJobMixIn.scheduleBuild2 default quiet parameter should be available as a static constant Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-11-25 18:27 Priority: Trivial Reporter: Chris Hunt As described in ParameterizedJobMixIn.scheduleBuild2, passing -1 as the quietPeriod causes the method to use the default. We should expose a static constant e.g. USE_DEFAULT_QUIET_PERIOD so plugin authors do not have to keep a named value for it in their plugins to avoid warnings about "magic numbers". Add Comment
[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Craig Ringer commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build The comments here about "silently" failing the build make me think it'd be very good to capture the hudson.Abort exception and its stack. Then when the pipeline aborts, print "Pipeline aborted. (See stack)", with "(See stack)" as a ConsoleAnnotation that lets you view the stack that led to the abort. Even "Pipeline aborted in 'build' step at line '42'" would be a massive help though. 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-52035) (Jenkins integration with HP PC for Perf testing)Jenkins doesnt show raw results or complete analysis file , it only shows HTML file as result.
Title: Message Title Daniel Danan commented on JENKINS-52035 Re: (Jenkins integration with HP PC for Perf testing)Jenkins doesnt show raw results or complete analysis file , it only shows HTML file as result. Hi Saurabh, Currently, the Performance Center plugin running test is only able to download html result analysis result. The raw result is not downloaded to the workspace of Jenkins job because it can be quite voluminous and it can be retrieved from the Performance Center project itself. regards, Daniel 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54843 Maven Enforcer Plugin crashes with java.level=11 Change By: Baptiste Mathus Assignee: Baptiste Mathus 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Baptiste Mathus started work on JENKINS-54843 Change By: Baptiste Mathus 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-54849) SVN_REVISION and/or SVN_REVISION_X not being set
Title: Message Title
Kartik Rathore updated an issue
Jenkins / JENKINS-54849
SVN_REVISION and/or SVN_REVISION_X not being set
Change By:
Kartik Rathore
Using Jenkins 2.138.3 and Subversion plugin on a windows machine. When doing a checkout from SVN server, SVN_REVISION environment variable isn't available as when trying to get the value all it return is empty string.I have tried to use ${SVN_REVISION} & ${SVN_REVISION_1} but none of them return any revision number.As suggested on stack overflow tried downgrading to subversion 2.10.3 but it still didnt work.https://stackoverflow.com/questions/53234867/svn-revision-variable-not-returning-checkout-revision-in-jenkins Additionally,After i downgraded SVNPlugin and then updated it again i now manage to get the SVN revision being set. However if i have an external set for the SVN repository i cannot access the external repository using SVN_REVISION_2SVN_REVISION_1 now returns the revision of teh actual repository.
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-54849) SVN_REVISION and/or SVN_REVISION_X not being set
Title: Message Title Kartik Rathore updated an issue Jenkins / JENKINS-54849 SVN_REVISION and/or SVN_REVISION_X not being set Change By: Kartik Rathore Environment: Jenkins v2.138.3Subversion plugin 2.12.1Connecting to VisualSVN repositoriedWindows OS (Win 10) Freestyle project job 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-54849) SVN_REVISION and/or SVN_REVISION_X not being set
Title: Message Title
Kartik Rathore created an issue
Jenkins / JENKINS-54849
SVN_REVISION and/or SVN_REVISION_X not being set
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
subversion-plugin
Created:
2018-11-25 13:15
Environment:
Jenkins v2.138.3 Subversion plugin 2.12.1 Connecting to VisualSVN repositoried Windows OS (Win 10)
Priority:
Minor
Reporter:
Kartik Rathore
Using Jenkins 2.138.3 and Subversion plugin on a windows machine. When doing a checkout from SVN server, SVN_REVISION environment variable isn't available as when trying to get the value all it return is empty string. I have tried to use ${SVN_REVISION} & ${SVN_REVISION_1} but none of them return any revision number. As suggested on stack overflow tried downgrading to subversion 2.10.3 but it still didnt work. https://stackoverflow.com/questions/53234867/svn-revision-variable-not-returning-checkout-revision-in-jenkins
Add Comment
[JIRA] (JENKINS-52397) Org Scan blows up when repository has no tags
Title: Message Title Yves Schumann commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags I'm spotting this regardless if there are tags or not, which breaks a lot of stuff right now. We're running Jenkins 2.152 and GitHub-Branch-Source-Plugin 2.4.1. Any ideas how to fix or a workaround? 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-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title Mez Pahlan resolved as Fixed Jenkins / JENKINS-54576 hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder' Change By: Mez Pahlan Status: In Progress Resolved 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco We are near to Surefire 3.0.0-M2 release. I have made a fix for this issue. There is a new XSD version 3.0 and documentation explaining the decisions, see index.apt.vm. I have pushed a branch SUREFIRE-1590 on GitHub. Please review it. Thx. 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished Jesse Glick Who should handle this issue? I am doing an internal workshop in my company about Jenkins on December 3rd and this issue is a big problem. 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-54848) Support Gherkin jobs in Jenkins - pipeline as code
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-54848 Support Gherkin jobs in Jenkins - pipeline as code Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-11-25 08:49 Priority: Major Reporter: Radi Berkovich 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-54545) Promisify the plugin deletion
Title: Message Title Jen Varela Lijó edited a comment on JENKINS-54545 Re: Promisify the plugin deletion Hi [~batmat]! I would like to give a try to this particular one. I have a year of experience developing in Java / Node and have roughly used Jenkins to run e2e tests, I'd like to get more familiar with the whole Jenkins ecosystem, so I thought contributing would be a good idea :) Is Evergreen a good point to start for a beginner? Cheers! 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-54545) Promisify the plugin deletion
Title: Message Title Jen Lijó commented on JENKINS-54545 Re: Promisify the plugin deletion Hi Baptiste Mathus! I would like to give a try to this particular one. I have a year of experience developing in Java / Node and I'd like to get more familiar with Jenkins so I thought contributing would be a good idea Is Evergreen a good point to start for a beginner? Cheers! 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.
