[JIRA] (JENKINS-51092) Two Factor Auth in Github Breaks Authentication for Github Organization
Title: Message Title Zhelyan Panchev commented on JENKINS-51092 Re: Two Factor Auth in Github Breaks Authentication for Github Organization Any progress on 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-41422) Assignment in if statements does not work
Title: Message Title
Zhelyan Panchev created an issue
Jenkins / JENKINS-41422
Assignment in if statements does not work
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/25 12:23 PM
Environment:
Jenkins 2.42 Pipeline 2.4 workflow-cps 2.24
Labels:
pipeline
Priority:
Minor
Reporter:
Zhelyan Panchev
The following fails in pipeline scripts (the if statement always evaluates to false)
def getStatus(){
//
"Ready"
}
//
def acceptedStatuses = ["Ready", "Updated", "Failed" ]
def status
if(acceptedStatuses.contains((status = getStatus({
// never called
}
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Zhelyan Panchev updated an issue Jenkins / JENKINS-40285 global libraries test harness Change By: Zhelyan Panchev related to JENKINS-33925 There aren't any standards and guidelines regarding the testing of shared pipeline libraries.The expected folder structure (https://issues.jenkins-ci.org/browse/JENKINS-33925) doesn't play well with Maven or Gradle and it isn't clear whether committing and pushing anything else but the expected folder tree would break the implementation.I couldn't find any examples apart from https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.javaTried to integrate a similar approach into an example standard shared library but it's of limited use, see https://github.com/zhelyan/jenkins-pipeline-test-harnessAny hints? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Zhelyan Panchev updated an issue Jenkins / JENKINS-40285 global libraries test harness Change By: Zhelyan Panchev +underlined text+ related to JENKINS-33925There aren't any standards and guidelines regarding the testing of shared pipeline libraries.The expected folder structure (https://issues.jenkins-ci.org/browse/JENKINS-33925) doesn't play well with Maven or Gradle and it isn't clear whether committing and pushing anything else but the expected folder tree would break the implementation.I couldn't find any examples apart from https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.javaTried to integrate a similar approach into an example standard shared library but it's of limited use, see https://github.com/zhelyan/jenkins-pipeline-test-harnessAny hints? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Zhelyan Panchev updated an issue Jenkins / JENKINS-40285 global libraries test harness Change By: Zhelyan Panchev +underlined text+ related to JENKINS-33925There aren't any standards and guidelines regarding the testing of shared pipeline libraries.The expected folder structure (https://issues.jenkins-ci.org/browse/JENKINS-33925) doesn't play well with Maven or Gradle and it isn't clear whether committing and pushing anything else but the expected folder tree would break the implementation.I couldn't find any examples apart from https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.javaTried to integrate a similar approach into an example standard shared library but it's of limited use, see https://github.com/zhelyan/jenkins-pipeline-test-harnessAny hints? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-40285) global libraries test harness
Title: Message Title Zhelyan Panchev created an issue Jenkins / JENKINS-40285 global libraries test harness Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Dec/07 5:03 PM Labels: test-harness Priority: Major Reporter: Zhelyan Panchev related to JENKINS-33925 There aren't any standards and guidelines regarding the testing of shared pipeline libraries. The expected folder structure (https://issues.jenkins-ci.org/browse/JENKINS-33925) doesn't play well with Maven or Gradle and it isn't clear whether committing and pushing anything else but the expected folder tree would break the implementation. I couldn't find any examples apart from https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.java Tried to integrate a similar approach into an example standard shared library but it's of limited use, see https://github.com/zhelyan/jenkins-pipeline-test-harness Any hints? Add
[JIRA] (JENKINS-40185) The links in the slack notifications don't resolve
Title: Message Title
Zhelyan Panchev updated an issue
Jenkins / JENKINS-40185
The links in the slack notifications don't resolve
Change By:
Zhelyan Panchev
I am using {{CucumberReportPublisher}} to publish the Cucumber reports. I can browse the report in Jenkins, links, captured screenshots and trend graphs all work fine.I then added {{cucumber-slack-notifier}} and although it does send the result summary to Slack the links in the Slack message don't resolve as they don't include the job name:Here's the job:{code:java}node { // CucumberReportPublisher step here cucumberSlackSend channel: '#test', failOnError: true, json: '.cucumber/features.json'}{code}Here's the url to one of the features in the published Cucumber report in Jenkins:{{https://jenkins/job/ProjectA/job/DEVOPS-309_capture-cucumber-reports/2/cucumber-html-reports/report-feature_features-add_new_client-feature.html}}Link to the same feature in the Slack message:{{https://jenkins/job/DEVOPS-309_capture-cucumber-reports/2/cucumber-html-reports/features/add_new_client-feature.html}}Link to the build in the Slack message:{{https://jenkins/job/DEVOPS-309_capture-cucumber-reports/2/cucumber-html-reports/}}The actual working link:{{https://jenkins/job/Casebook/job/DEVOPS-309_capture-cucumber-reports/2/ cucumber-html-reports }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40185) The links in the slack notifications don't resolve
Title: Message Title
Zhelyan Panchev created an issue
Jenkins / JENKINS-40185
The links in the slack notifications don't resolve
Issue Type:
Bug
Assignee:
Gareth Evans
Components:
cucumber-slack-notifier-plugin
Created:
2016/Dec/02 9:48 AM
Environment:
Jenkins 2.33, pipeline 2.4, cucumber-slack-notifier 0.8.3
Labels:
plugin 2.0
Priority:
Minor
Reporter:
Zhelyan Panchev
I am using CucumberReportPublisher to publish the Cucumber reports. I can browse the report in Jenkins, links, captured screenshots and trend graphs all work fine. I then added cucumber-slack-notifier and although it does send the result summary to Slack the links in the Slack message don't resolve as they don't include the job name: Here's the job:
node {
// CucumberReportPublisher step here
cucumberSlackSend channel: '#test', failOnError: true, json: '.cucumber/features.json'
}
Here's the url to one of the features in the published Cucumber report in Jenkins: https://jenkins/job/ProjectA/job/DEVOPS-309_capture-cucumber-reports/2/cucumber-html-reports/report-feature_features-add_new_client-feature.html Link to the same feature in the Slack message: https://jenkins/job/DEVOPS-309_capture-cucumber-reports/2/cucumber-html-reports/features/add_new_client-feature.html Link to the build in
[JIRA] (JENKINS-34428) workflow-cps-global-lib: inheritance (extends) not working
Title: Message Title Zhelyan Panchev commented on JENKINS-34428 Re: workflow-cps-global-lib: inheritance (extends) not working I can extend abstract classes but calling super.somemethod() from the implementation throws StackOverflow exception Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Zhelyan Panchev commented on JENKINS-35140 Re: JsonSlurper does not work after updating to Jenkins 2.x weird but now it works in Jenkins 2.7 with or without @NonCPS.. I don't think anything changed apart from restarting Jenkins couple of times and upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Zhelyan Panchev updated an issue
Jenkins / JENKINS-35140
JsonSlurper does not work after updating to Jenkins 2.x
Change By:
Zhelyan Panchev
Comment:
same code works in Jenkins 2.7 with or without {{\@NonCPS}} after upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Zhelyan Panchev edited a comment on JENKINS-35140
Re: JsonSlurper does not work after updating to Jenkins 2.x
same code works in Jenkins 2.7 with or without {{\@NonCPS}} after upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Zhelyan Panchev commented on JENKINS-35140 Re: JsonSlurper does not work after updating to Jenkins 2.x same code works in Jenkins 2.7 with or without @NonCPS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Zhelyan Panchev commented on JENKINS-35140
Re: JsonSlurper does not work after updating to Jenkins 2.x
I cannot get it to work:
node{
echo parseText(' { "foo": "bar" } ') // prints null
}
@NonCPS
def parseText(txt){
return new groovy.json.JsonSlurper().parseText(txt)
}
Jenkins 2.6 / 2.7 Pipeline 2.1
No exceptions, pipeline finishes successfully
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
