[JIRA] (JENKINS-50260) lock step interacts badly with timeout step
Title: Message Title
Tomas Bjerre commented on JENKINS-50260
Re: lock step interacts badly with timeout step
I tried using: Build Timeout Plugin 1.19 Lockable Resource Plugin 2.8-SNAPSHOT And with pipeline:
lock('myresource') {
println "locked"
timeout(time: 2, unit: 'SECONDS') {
println "sleep..."
sleep 10
println "sleep done !!"
}
println "leaving timeout"
}
println "after lock"
timeout(time: 2, unit: 'SECONDS') {
println "locking..."
lock('myresource') {
println "locked, sleeping..."
sleep 10
println "sleep done !!"
}
println "left lock"
}
println "left timeout"
The log shows:
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] lock
Trying to acquire lock on [myresource]
Resource [myresource] did not exist. Created.
Lock acquired on [myresource]
[Pipeline] {
[Pipeline] echo
locked
[Pipeline] timeout
Timeout set to expire in 2 sec
[Pipeline] {
[Pipeline] echo
sleep...
[Pipeline] sleep
Sleeping for 10 sec
Cancelling nested steps due to timeout
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
Lock released on resource [myresource]
[Pipeline] // lock
[Pipeline] End of Pipeline
Timeout has been exceeded
Finished: ABORTED
Would help if anyone can reproduce it with a sample pipeline and plugin versions.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre commented on JENKINS-60951 Re: NPE Generic Webhook trigger plugin invoke I interpret the stacktrace as if it is not a problem with Generic Webhook Trigger Plugin. Unassigning myself and removing the generic-webhook-trigger component. I also interpret it as a temporary problem that was solved with a reboot. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.47.1580742780121%40Atlassian.JIRA.
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre updated an issue Jenkins / JENKINS-60951 NPE Generic Webhook trigger plugin invoke Change By: Tomas Bjerre Component/s: generic-webhook-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.45.1580742720224%40Atlassian.JIRA.
[JIRA] (JENKINS-60951) NPE Generic Webhook trigger plugin invoke
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-60951 NPE Generic Webhook trigger plugin invoke Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204410.1580741728000.43.1580742600670%40Atlassian.JIRA.
[JIRA] (JENKINS-58285) getJiraVersions constructor returns null
Title: Message Title Tomas Bjerre closed an issue as Incomplete Jenkins / JENKINS-58285 getJiraVersions constructor returns null Change By: Tomas Bjerre Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200349.156199046.13141.1561990860520%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58285) getJiraVersions constructor returns null
Title: Message Title Tomas Bjerre commented on JENKINS-58285 Re: getJiraVersions constructor returns null It is not possible to investigate this whitout more details. There is currently nothing in this issue that indicates it has anything to do with the Generic Webhook Trigger Plugin. If you think it has anything to do with the plugin, open issue here and pay attention to the issue template: https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/new Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200349.156199046.13139.1561990800154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-57390 Enable credentials in triggers using declarative pipelines Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199172.155743169.22475.1557431820046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title
Tomas Bjerre updated an issue
Jenkins / JENKINS-57390
Enable credentials in triggers using declarative pipelines
Change By:
Tomas Bjerre
h1. BackgroundThis issue originates from this issue in Generic Webhook Trigger Plugin: [https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/107]The reporter is using declarative pipeline.The user wants to get the credential, secret text, and use it when configuring triggers. More specifically as value of the 'token' configuration parameter in the plugin.Something like this:{code:java}... environment {JENKINS_TOKEN = credentials('JENKINS_TOKEN') } triggers {GenericTrigger( genericVariables: [ ... ], causeString: 'Triggered by $image', token: env.JENKINS_TOKEN, printContributedVariables: true, printPostContent: true) }...{code}h1. ProblemThe problem is that the credential, or variables form the environment block, is not available in the triggers block.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title
Tomas Bjerre created an issue
Jenkins / JENKINS-57390
Enable credentials in triggers using declarative pipelines
Issue Type:
Improvement
Assignee:
Tomas Bjerre
Components:
generic-webhook-trigger-plugin, pipeline-model-definition-plugin
Created:
2019-05-09 19:54
Labels:
pipeline
Priority:
Major
Reporter:
Tomas Bjerre
Background This issue originates from this issue in Generic Webhook Trigger Plugin: https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/107 The reporter is using declarative pipeline. The user wants to get the credential, secret text, and use it when configuring triggers. More specifically as value of the 'token' configuration parameter in the plugin. Something like this:
...
environment {
JENKINS_TOKEN = credentials('JENKINS_TOKEN')
}
triggers {
GenericTrigger(
genericVariables: [
...
],
causeString: 'Triggered by $image',
token: env.JENKINS_TOKEN,
printContributedVariables: true,
printPostContent: true
)
}
...
Problem The problem is that credential, variables form the environment block, is not available in the triggers block.
[JIRA] (JENKINS-51538) tmp dir filled up with scanXXXX.xml.gz files
Title: Message Title Tomas Bjerre commented on JENKINS-51538 Re: tmp dir filled up with scan.xml.gz files My workaround was to create a scheduled job that, once a day, run something like "rm /tmp/scan*.xml.gz" 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-55733) Wrong parsing of CppCheck results
Title: Message Title Tomas Bjerre commented on JENKINS-55733 Re: Wrong parsing of CppCheck results Each "violation" in the Violations Lib is intended to be one problem/issue that is subject to change. In contrast to being one "type" of problem. If the reassigning occurs in rectangular_frustum_selector.cpp on line 53 and 51, and if conditions on 346 and 335 are always true, then the Violations Lib is working as intended. There are 2 types of errors and each type is detected 2 times. The Violations Lib, with its normalized model, should report 4 Violations in this case. If you need to group each type of Violation you will have to do something like looping through them and transform the list of Violations to, perhaps, a Map> where String would be each distinct message of the Violations. 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-54895) Jenkins build used wrong commit number
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-54895 Jenkins build used wrong commit number Change By: Tomas Bjerre Assignee: Tomas Bjerre 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-54122) Jenkins failing to list the changes detected from git repositories
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-54122 Jenkins failing to list the changes detected from git repositories Change By: Tomas Bjerre Assignee: Tomas Bjerre 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-51538) tmp dir filled up with scanXXXX.xml.gz files
Title: Message Title Tomas Bjerre created an issue Jenkins / JENKINS-51538 tmp dir filled up with scan.xml.gz files Issue Type: Bug Assignee: Justin Young Components: nexus-platform-plugin Created: 2018-05-25 06:58 Priority: Major Reporter: Tomas Bjerre Plugin version: 3.0.20180214-134325.e135900 Jenkins version: 2.89.2 Problem We are seeing a lot of files in our /tmp folder. Example: scan9001816880777266595.xml.gz They are probably created by this plugin here: https://github.com/jenkinsci/nexus-platform-plugin/blob/master/src/main/java/org/sonatype/nexus/ci/iq/RemoteScanResult.groovy#L33 This is causing our tmp partition to fill up and master node eventually goes offline. Suggested fix Don't fill up tmp dir. Add Comment
[JIRA] (JENKINS-51019) Enable caching of node_modules
Title: Message Title Tomas Bjerre created an issue Jenkins / JENKINS-51019 Enable caching of node_modules Issue Type: New Feature Assignee: Tim Downey Components: pipeline-npm-plugin Created: 2018-04-26 12:41 Priority: Minor Reporter: Tomas Bjerre Our jobs are spending a lot of time downloading npm packages. I came across this: https://dev.to/khsing/speed-up-jenkins-with-npm-build-3pc Perhaps that can be added to this plugin? Hash the package.json and store node_modules folders in a cached, globally available, folder. Add Comment
[JIRA] (JENKINS-50990) Security exception in GitChangelogStep (JEP-200)
Title: Message Title Tomas Bjerre commented on JENKINS-50990 Re: Security exception in GitChangelogStep (JEP-200) Releasing a fix in 2.3 now. Sergey Egorov this will be available in the update site within a few hours. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50990) Security exception in GitChangelogStep (JEP-200)
Title: Message Title Tomas Bjerre updated JENKINS-50990 Jenkins / JENKINS-50990 Security exception in GitChangelogStep (JEP-200) Change By: Tomas Bjerre Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50990) Security exception in GitChangelogStep (JEP-200)
Title: Message Title Tomas Bjerre commented on JENKINS-50990 Re: Security exception in GitChangelogStep (JEP-200) I just tried to reproduce this. Was not able to so in 2.118. Not when running in Docker with latest image and not with mvn hpi:run -Djenkins.version=2.118. I was able to create changelogs without problems in both cases. This: https://jenkins.io/blog/2018/01/13/jep-200/ Sounds like I need to add a hudson.remoting.ClassFilter like this: https://github.com/jenkinsci/git-changelog-plugin/blob/feature/JENKINS-50990/src/main/resources/META-INF/hudson.remoting.ClassFilter Oleg Nenashev Should I add the ClassFilter-file and make a release? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Tomas Bjerre closed an issue as Won't Fix Jenkins / JENKINS-38164 Group changelog entries by Jenkins build numbers Change By: Tomas Bjerre Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40760) Use Credentials defined in GitHub plugin
Title: Message Title Tomas Bjerre closed an issue as Won't Fix This would add complexity to the implementation. And you can easily use the same credentials in a pipeline. https://jenkins.io/doc/pipeline/steps/credentials-binding/ I dont want to implement this. Jenkins / JENKINS-40760 Use Credentials defined in GitHub plugin Change By: Tomas Bjerre Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-49442) Builds hanging on htmlpublisher
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-49442 Builds hanging on htmlpublisher Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49392) Violations plugin freezes project settings screen
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-49392 Violations plugin freezes project settings screen Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41005) Violations plugin makes concurrent builds wait
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-41005 Violations plugin makes concurrent builds wait Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40987) Exception when saving the job configuration
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-40987 Exception when saving the job configuration Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44919) Pipeline Snippet doesn't generate useful output
Title: Message Title Tomas Bjerre closed an issue as Cannot Reproduce Cannot reproduced this. Perhaps a bug that has been fixed in another issue. Jenkins / JENKINS-44919 Pipeline Snippet doesn't generate useful output Change By: Tomas Bjerre Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-38949) Respect included/excluded regions in git
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-38949 Respect included/excluded regions in git Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Tomas Bjerre commented on JENKINS-38164 Re: Group changelog entries by Jenkins build numbers Here is an example that recursively gets the older builds: https://stackoverflow.com/questions/38084806/how-to-get-the-changes-since-the-last-successful-build-in-jenkins-pipeline Here is an example that gets the changesets of builds: https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job- Using that in combination with this plugin should solve this. def changelogString = gitChangelog returnType: 'STRING', from: [type: 'COMMIT', value: 'commit hash here'], to: [type: 'COMMIT', value: 'next build commit hash here'], template: """ the template... """ println changelogString Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-38164 Group changelog entries by Jenkins build numbers Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title Tomas Bjerre closed an issue as Won't Fix Jenkins / JENKINS-43362 Allow for setting how commit hashes should be abbreviated Change By: Tomas Bjerre Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title
Tomas Bjerre edited a comment on JENKINS-43362
Re: Allow for setting how commit hashes should be abbreviated
The problem here is to find out how to do that with JGit... I can't find it in any docs.But what one can do for now is to use one of these attributes on the commit instance: * {{hash}} * {{hashFull}} {{}} [https://github.com/tomasbjerre/git-changelog-lib]I'll close this one and you can open an issue in the lib if this is still something that you need.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title
Tomas Bjerre commented on JENKINS-43362
Re: Allow for setting how commit hashes should be abbreviated
The problem here is to find out how to do that with JGit... I can't find it in any docs. But what one can do for now is to use one of these attributes on the commit instance:
hash
hashFull{{}}
https://github.com/tomasbjerre/git-changelog-lib I'll close this one and you can open an issue in the lib if this is still something that you need.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-43362) Allow for setting how commit hashes should be abbreviated
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-43362 Allow for setting how commit hashes should be abbreviated Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45838) MR/PR or Tag push from Gitlab to multibranch pipeline
Title: Message Title Tomas Bjerre commented on JENKINS-45838 Re: MR/PR or Tag push from Gitlab to multibranch pipeline You can use Generic Webhook Trigger Plugin: https://github.com/jenkinsci/generic-webhook-trigger-plugin You will need to setup a filter to trigger only for specific events. That is documented here: https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/src/test/resources/org/jenkinsci/plugins/gwt/bdd/gitlab And here is something to get you started with the Jenkinsfile: https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/sandbox/multibranch.jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-45930 Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Tomas Bjerre commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 For the record, future of violations plugin is discussed here: https://github.com/jenkinsci/violations-plugin/issues/88 I don't mind releasing it. Should require minimal effort from my part to maintain as I already maintain the lib for a bunch of other tools. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-40987) Exception when saving the job configuration
Title: Message Title Tomas Bjerre commented on JENKINS-40987 Re: Exception when saving the job configuration Use the warnings-plugin, https://github.com/jenkinsci/violations-plugin/issues/88 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-34530) Jenkins test harness does not support Jenkins 2.x
Title: Message Title Tomas Bjerre commented on JENKINS-34530 Re: Jenkins test harness does not support Jenkins 2.x Vegard Endresen I also encountered this. I changed test-harness to latest version, and that works. Now I have: org.jenkins-ci.plugins plugin 2.23 2.0 1.115 2.19 false 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library https://github.com/jenkinsci/violation-comments-to-stash-plugin https://github.com/tomasbjerre/violation-comments-to-github-maven-plugin https://github.com/tomasbjerre/violation-comments-to-github-gradle-plugin But I think I've made my points here. Don't have anything more to add to this discussion. Tuukka Mustonen: We clearly have very different views on how this should be solved so I don't see this happening. I think what I have in violations-lib is the perfect approach and if you need any parser implemented, just open an issue there! =) 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] (JENKINS-17434) Allow to call parsers without jenkins (standalone)
Title: Message Title Tomas Bjerre commented on JENKINS-17434 Re: Allow to call parsers without jenkins (standalone) You may want to have a look at: https://github.com/tomasbjerre/violations-lib 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library "if you don't like libraries" I do like libraries. I dont like libraries that polutes my classpath. I dont want to force users of my library into using a specific version of some other library. "why don't you use java logging and remove slf4j, too?" I was using slf4j-api, and only the basic functionality. That is very unlikely to casue problems. But on the other hand I only do very little logging so I actually removed slf4j-api too. The FindBugs report is tricky, yes. If there is a findbugs-parser ready and working using digester then that, to me, is a valid argument for having digester on the classpath. And use shading to avoid classpath collisions. 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library 1. Sort of yes. If you take Guava for example. I have been using this method alot: https://google.github.io/guava/releases/19.0/api/docs/com/google/common/base/Objects.html#firstNonNull(T, T) As you can read there it says "scheduled for removal in June 2016". If the library was using that method then anyone trying to use the library in an application with latest Guava would get ClassNotFoundException if they have latest Guava on classpath, or they would have to downgrade their Guava to the older one used by the library. Also commons-digester3 (https://repo1.maven.org/maven2/org/apache/commons/commons-digester3/3.2/commons-digester3-3.2.pom) adds cglib, commons-beanutils, commons-logging + whatever libraries they depend on. A good library does not force the user of the library into using a specific version of a utility library like this. I dont see the need to use anything else but the standard library here. Show me an example and I may change my mind =) 3. Yes, .size() would work. 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library 1a I use the library also in Gradle and Maven plugins. Others may use it in whatever application they want, perhaps another CI server. Having a dependency to Jenins just does not make sense for a library whose only task is to read and parse text-files. 1b I prefer to make it Java 7 compatible because its still used by alot of people. Unnecessary libraries on the classpath will be a problem for users of the library. For example, they may already have another version of Apache commons already on the classpath. It may be there because of another dependency or because they need it themselves. They would have to exclude dependencies and sometimes it will be impossible to resolve the situation and find a version that is compatible with all libraries using it. I have been able to implement alot of parsers this way, the library is very clean, very easy to work with and understand for anyone familiar with Java. I'd like to keep it that way. 2 That to me sounds like something other then reading and parsing text files. Not a problem that should be solved by the library. 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre edited a comment on JENKINS-40439 Re: Move parsers into external library 1. No. Just SLF4J and Guava https://github.com/tomasbjerre/violations-lib/blob/master/build.gradle#L43 .2. Its a list of Violations https://github.com/tomasbjerre/violations-lib/blob/master/src/main/java/se/bjurr/violations/lib/model/Violation.java3. No.When it comes to defining an API I am pretty much happy with what I have. But I am open for suggestions! I may find some time to get rid of the Guava dependency. I took a quick look at analysis-model. The amount of dependencies are a show stopper for me. I would rather spend time on making the parsing algorithms use only functionality from the standard library (1.7). 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] (JENKINS-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library 1. No. Just SLF4J and Guava https://github.com/tomasbjerre/violations-lib/blob/master/build.gradle#L43 . 2. Its a list of Violations https://github.com/tomasbjerre/violations-lib/blob/master/src/main/java/se/bjurr/violations/lib/model/Violation.java 3. No. When it comes to defining an API I am pretty much happy with what I have. But I am open for suggestions! I may find some time to get rid of the Guava dependency. I took a quick look at analysis-model. The amount of dependencies are a show stopper for me. I would rather spend time on making the parsing algorithms use only functionality from the standard library (1.7). 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] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Tomas Bjerre commented on JENKINS-34205 Re: Add support for workflow/pipeline to the violations plugin https://github.com/jenkinsci/violations-plugin/issues/91 And also: https://github.com/jenkinsci/violations-plugin/issues/88 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] (JENKINS-33423) configuring maven-checkstyle-plugin:2.17:checkstyle error cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre resolved as Duplicate https://issues.jenkins-ci.org/browse/JENKINS-28880 Jenkins / JENKINS-33423 configuring maven-checkstyle-plugin:2.17:checkstyle error cannot change build result while in COMPLETED Change By: Tomas Bjerre Status: Open Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-36487) Update code violation comments to Atlassian-hosted BitBucket Cloud
Title: Message Title Tomas Bjerre closed an issue as Fixed Jenkins / JENKINS-36487 Update code violation comments to Atlassian-hosted BitBucket Cloud Change By: Tomas Bjerre Status: Open Closed Resolution: Fixed 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] (JENKINS-36487) Update code violation comments to Atlassian-hosted BitBucket Cloud
Title: Message Title Tomas Bjerre commented on JENKINS-36487 Re: Update code violation comments to Atlassian-hosted BitBucket Cloud There is not such plugin. So not possible. 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre closed an issue as Fixed Jenkins / JENKINS-37196 DSL for Violation Comments to GitHub Plugin Change By: Tomas Bjerre Status: Open Closed Resolution: Fixed 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin The wiki is a bit slow. But 1.14 is in the update site: http://mirror.xmission.com/jenkins/updates/current/update-center.json 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin I just made a new release, changed the DSL a bit. Use the examples from the README at: https://github.com/jenkinsci/violation-comments-to-github-plugin 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title
Tomas Bjerre commented on JENKINS-37196
Re: DSL for Violation Comments to GitHub Plugin
I just made a release, will be in the update site within a few hours. The DSL is now:
violationsToGitHubRecorder {
createSingleFileComments(boolean value)
createCommentWithAllSingleFileComments(boolean value)
repositoryName(String value)
repositoryOwner(String value)
password(String value)
username(String value)
oAuth2Token(String value)
pullRequestId(String value)
gitHubUrl(String value)
commentOnlyChangedContent(boolean value)
violationConfigs {
violationConfig {
reporter(String value)
pattern(String value)
}
}
usernamePasswordCredentialsId(String value)
useOAuth2Token(boolean value)
useUsernamePasswordCredentials(boolean value)
useUsernamePassword(boolean value)
}
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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin I was fiddling with this a bit but did not manage to do what you want. I found this commit: https://github.com/jenkinsci/ghprb-plugin/commit/882bbd79f73e2099c7c1125ce5994d0952cf4464 I think something like that is needed in this plugin to enable a nice DSL here. I may have time later today to look at it. 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre commented on JENKINS-37196 Re: DSL for Violation Comments to GitHub Plugin Also add: import org.jenkinsci.plugins.jvctg.config.ViolationConfig; import se.bjurr.violations.lib.reports.Reporter; There is an example in the readme at: https://github.com/jenkinsci/violation-comments-to-github-plugin 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] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title
Tomas Bjerre commented on JENKINS-37196
Re: DSL for Violation Comments to GitHub Plugin
You need to add violationConfigs like this:
violationsToGitHubRecorder {
createSingleFileComments(true)
createCommentWithAllSingleFileComments(false)
repositoryName(repoName)
repositoryOwner(‘jen1')
password('')
username('')
oAuth2Token('')
pullRequestId('$
{ghprbPullId}
')
gitHubUrl('https://github.inmobi.com/api/v3')
commentOnlyChangedContent(true)
usernamePasswordCredentialsId('false')
useOAuth2Token(false)
useUsernamePassword(false)
useUsernamePasswordCredentials(true),
violationConfigs: [
new ViolationConfig(Reporter.FINDBUGS, ".*/findbugs.*\\.xml\$")
]
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] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title Tomas Bjerre assigned an issue to peterkittreilly Jenkins / JENKINS-19260 Cannot parse codenarc xml, due to empty path attribute in element Package Change By: Tomas Bjerre Assignee: Tomas Bjerre peterkittreilly 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] (JENKINS-28880) Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED"
Title: Message Title Tomas Bjerre assigned an issue to peterkittreilly Jenkins / JENKINS-28880 Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED" Change By: Tomas Bjerre Assignee: Tomas Bjerre peterkittreilly 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] (JENKINS-28880) Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED"
Title: Message Title Tomas Bjerre commented on JENKINS-28880 Re: Maven builds fail with "IllegalStateException: cannot change build result while in COMPLETED" My opinion is that this plugin should be rewritten. Its just a waste of time to try to fix all the bugs. https://github.com/jenkinsci/violations-plugin/issues/88 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] [git-changelog-plugin] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Tomas Bjerre commented on JENKINS-34886 Re: Jenkins Git Error Invalid ID No I'd say its Git Client Plugin. 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes This shouls be fixed now. Update to 1.22 and open issue again if not working! 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-34156 git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre edited a comment on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes This shouls should be fixed now. Update to 1.22 and open issue again if not working! 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes I think I found the problem, added test case for it here: https://github.com/tomasbjerre/git-changelog-lib/commit/ddfc0438c0fb09732162444b9dd7c2c33b60c195 But no solution yet... 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre commented on JENKINS-34156 Re: git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes What does your repo look like? What is the output of: git log --graph --full-history --all --color --date=short --pretty=format:"%Cred%x09%h %Creset%ad%Cgreen%d %Creset %s %C(bold)(%an)%Creset" What were the values you used as from and to commits? What did your template look like? 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] [git-changelog-plugin] (JENKINS-34156) git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-34156 git changelog, when given 2 SHA-1s, outputs a bunch of seemingly random changes Change By: Tomas Bjerre Assignee: Paul Wellner Bou Tomas Bjerre 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] [git-changelog-plugin] (JENKINS-34155) Git Changelog Plugin does not seem to take short SHA-1s as input
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-34155 Git Changelog Plugin does not seem to take short SHA-1s as input Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [git-changelog-plugin] (JENKINS-34155) Git Changelog Plugin does not seem to take short SHA-1s as input
Title: Message Title Tomas Bjerre commented on JENKINS-34155 Re: Git Changelog Plugin does not seem to take short SHA-1s as input Should be fixed in 1.19. I just released it, will be in the update sites within a few hours. 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-34075 Getting "Invalid id:" error when trying to create a very simple changelog Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre commented on JENKINS-34075 Re: Getting "Invalid id:" error when trying to create a very simple changelog If you dont add a template, nothing will be displayed. 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre commented on JENKINS-34075 Re: Getting "Invalid id:" error when trying to create a very simple changelog Same plugin 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre commented on JENKINS-34075 Re: Getting "Invalid id:" error when trying to create a very simple changelog Are you able to use the plugin if you select "first commit in repo" or "A branch or a tag"? 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre commented on JENKINS-34075 Re: Getting "Invalid id:" error when trying to create a very simple changelog yes 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] [git-changelog-plugin] (JENKINS-34075) Getting "Invalid id:" error when trying to create a very simple changelog
Title: Message Title Tomas Bjerre commented on JENKINS-34075 Re: Getting "Invalid id:" error when trying to create a very simple changelog Is this still a problem with 1.18? I made a few tests, with Jenkins 1.609.3, and it works for me. I tried generating changelog with same value for from/to commit. Tried with the variables you used in your example. I only get invalid Id if I try GIT_PREVIOUS_SUCCESSFUL_COMMIT or GIT_PREVIOUS_COMMIT when those dont resolve to any commit id (first build). 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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Tomas Bjerre commented on JENKINS-33301 Re: git-changelog: specifying references No problem =) 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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Tomas Bjerre commented on JENKINS-33301 Re: git-changelog: specifying references I guess you are refering to the printout from "GIt Publisher". Try to use the variables in "Git Changelog" task. 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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Tomas Bjerre commented on JENKINS-33301 Re: git-changelog: specifying references GIT_PREVIOUS_COMMIT is the previous built commit, so perhaps HEAD^1 but it can be any parent. Ok I see, i interpreted it as if he needed to have from as "successful" OR "not successful". Which is == true for GIT_PREVIOUS_COMMIT. He may use GIT_PREVIOUS_SUCCESSFUL_COMMIT to be sure that he uses the last successful. 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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Tomas Bjerre commented on JENKINS-33301 Re: git-changelog: specifying references Martin Kulich: Is your problem solved with setting from GIT_PREVIOUS_COMMIT and to GIT_COMMIT? Paul Wellner Bou: I dont understand what you mean here. He wrote "It would include specifying 'from' reference as 'last successful build' / ... and 'to' reference as 'current build'. ". And the from/to fields are expanded (https://github.com/jenkinsci/git-changelog-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitchangelog/perform/GitChangelogPerformer.java#L157) so the variables from Git Plugin should be available. I interpret the issue as if he wants to have this changelog on the current build, which is the one building GIT_COMMIT. 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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title
Tomas Bjerre edited a comment on JENKINS-33301
Re: git-changelog: specifying references
Are you using the Git Plugin? If so, you should be able to use the environment variables. Specify from commit as ${ GIT_COMMIT GIT_PREVIOUS_COMMIT } and to commit as ${ GIT_PREVIOUS_COMMIT GIT_COMMIT }https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
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] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title
Tomas Bjerre commented on JENKINS-33301
Re: git-changelog: specifying references
Are you using the Git Plugin? If so, you should be able to use the environment variables. Specify from commit as $ {GIT_COMMIT}
and to commit as $ {GIT_PREVIOUS_COMMIT}
https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
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] [git-changelog-plugin] (JENKINS-32111) git-changelog can be only applied to free-style project
Title: Message Title Tomas Bjerre resolved as Fixed Released in 1.3 Jenkins / JENKINS-32111 git-changelog can be only applied to free-style project Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title Tomas Bjerre commented on JENKINS-19260 Re: Cannot parse codenarc xml, due to empty path attribute in element Package This fix is only released in alpha versions. Available in experimental plugin repo or here: https://github.com/jenkinsci/violations-plugin/releases 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] [violations-plugin] (JENKINS-15248) Auto update violations unstable and heathly limits following a healthy build
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-15248 Auto update violations unstable and heathly limits following a healthy build Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [violations-plugin] (JENKINS-15248) Auto update violations unstable and heathly limits following a healthy build
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-15248 Auto update violations unstable and heathly limits following a healthy build Change By: Tomas Bjerre Assignee: peterkittreilly TomasBjerre 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] [violations-plugin] (JENKINS-14970) XML File pattern for JSLINT is not getting persisted.
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-14970 XML File pattern for JSLINT is not getting persisted. Change By: Tomas Bjerre Status: Open Resolved Assignee: peterkittreilly TomasBjerre Resolution: Fixed 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] [violations-plugin] (JENKINS-22364) Jenkins Violation Plugin Does Not Populate XML Filename Pattern
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-22364 Jenkins Violation Plugin Does Not Populate XML Filename Pattern Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed 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] [violations-plugin] (JENKINS-28880) Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre stopped work on JENKINS-28880 Change By: Tomas Bjerre Status: InProgress Open 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] [violations-plugin] (JENKINS-28762) violations plugin breaks jobs GUI and fail builds those configured with compiler warning
Title: Message Title Tomas Bjerre updated an issue Jenkins / JENKINS-28762 violations plugin breaks jobs GUI and fail builds those configured with compiler warning Change By: Tomas Bjerre Priority: Major Minor 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] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-19260 Cannot parse codenarc xml, due to empty path attribute in element Package Change By: Tomas Bjerre Status: Open Resolved Assignee: peterkittreilly TomasBjerre Resolution: Fixed 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] [violations-plugin] (JENKINS-28880) Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre commented on JENKINS-28880 Re: Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED We can easily make the consequence less severe, by catching the IllegalStateException and just log it. Then the violation reports will still be populated. But still, the build result wont be UNSTABLE, but instead SUCCESSFUL. https://github.com/jenkinsci/violations-plugin/pull/68 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] [violations-plugin] (JENKINS-28880) Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre assigned an issue to Tomas Bjerre Jenkins / JENKINS-28880 Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED Change By: Tomas Bjerre Assignee: peterkittreilly TomasBjerre 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] [violations-plugin] (JENKINS-28880) Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre started work on JENKINS-28880 Change By: Tomas Bjerre Status: Open InProgress 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] [violations-plugin] (JENKINS-28762) violations plugin breaks jobs GUI and fail builds those configured with compiler warning
Title: Message Title Tomas Bjerre commented on JENKINS-28762 Re: violations plugin breaks jobs GUI and fail builds those configured with compiler warning Sounds like something we really should not spend time on. Ok to close it? 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] [violations-plugin] (JENKINS-24178) Support pep257 validator
Title: Message Title Tomas Bjerre commented on JENKINS-24178 Re: Support pep257 validator Can you supply a sample report-file? 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.
