[JIRA] [configurationslicing-plugin] (JENKINS-20319) Configuration slicing resets send separate emails... for Email notification
Title: Message Title Torbjrn Axelsson closed an issue as Fixed Thanks. Jenkins / JENKINS-20319 Configuration slicing resets send separate emails... for Email notification Change By: Torbjrn Axelsson Status: Resolved Closed 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] [coverity] (JENKINS-21481) Coverity plugin 1.3.0 crashes job with CSA/CC 6.5.1, bad parsing of VERSION
Torbjörn Axelsson commented on JENKINS-21481 Coverity plugin 1.3.0 crashes job with CSA/CC 6.5.1, bad parsing of VERSION We just upgrade to Coverity 7.0.3 and got this problem, however: # grep external /opt/cov-analysis/VERSION externalVersion=7.0.3 So we have the same problem, but it seems that the externalVersion is there in the file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson created JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 19/Dec/13 3:44 PM Description: When I pulled the scm-config repository I was suprised to se 6 GB of data being pulled down. I seems that all the artifacts are stored in git. Is this really intended? The artifacts are not xml files, it is the content of jobs/buildname/builds/ that is stored. I thought this was just storing configuration. Project: Jenkins Priority: Major Reporter: Torbjörn Axelsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? We are running 0.0.7.3 on Jenkins 1.543 However, upon closer examination the files saved are from 2013-10-31_11-17-51/ (and earlier) at which point we might very well have used a version prior to 0.0.7.2 Should have looked closer before reporting the problem. Thanks for a very good (and addictive) plugin and a really rapid response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson closed JENKINS-21096 as Fixed scm-sync-configuration: Store artifacts in git, is this really intended? Change By: Torbjörn Axelsson (19/Dec/13 4:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Torbjörn Axelsson resolved JENKINS-21096 as Fixed scm-sync-configuration: Store artifacts in git, is this really intended? The issues is fixed in a version we already have upgraded to. Change By: Torbjörn Axelsson (19/Dec/13 4:44 PM) Status: Open Resolved Assignee: FrédéricCamblor TorbjörnAxelsson Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-18200) Build flow job: UI blocks for each job disappear from past jobs if configuration has changed.
Torbjörn Axelsson commented on JENKINS-18200 Build flow job: UI blocks for each job disappear from past jobs if configuration has changed. The information is currently visilable in the log file for the build flow job, which is one way I consider to extract the information for a stop-gap tool to do visualization until build-flow is fixed. (Unless we get someone to fix build-flow, then we will send in a patch instead.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
