[JIRA] [jboss] (JENKINS-19045) No page found 'digest.jelly'
Radim Kolar commented on JENKINS-19045 No page found digest.jelly it works in version 523, broken in 524, 525 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] [core] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
dogfood commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers Integrated in jenkins_main_trunk #2781 FIXED JENKINS-18677 (Revision 47de54d070f67af95b4fefb6d006a72bb31a5cb8) Result = SUCCESS kohsuke : 47de54d070f67af95b4fefb6d006a72bb31a5cb8 Files : pom.xml core/src/main/java/hudson/PluginManager.java core/pom.xml core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/ClassicPluginStrategy.java changelog.html 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] [core] (JENKINS-19045) No page found 'digest.jelly'
JulB4 updated JENKINS-19045 No page found digest.jelly This bug is related to core not jboss plugin. I know the component name is a bit confusing Change By: JulB4 (03/Aug/13 8:13 AM) Component/s: core Component/s: jboss 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] [core] (JENKINS-19045) No page found 'digest.jelly'
JulB4 updated JENKINS-19045 No page found digest.jelly Change By: JulB4 (03/Aug/13 8:14 AM) Assignee: JulB4 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] [copyartifact] (JENKINS-19057) ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
ikedam created JENKINS-19057 ProjectName with variables in CopyArtifact 1.26 is improperly upgraded. Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 03/Aug/13 8:36 AM Environment: CopyArtifact 1.26, 1.27 Project: Jenkins Priority: Major Reporter: ikedam 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] [copyartifact] (JENKINS-19057) ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
ikedam
updated JENKINS-19057
ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
Change By:
ikedam
(03/Aug/13 8:45 AM)
Description:
#InstallCopyArtifact1.25.#Createamulti-configurationprojectlikethis:**projectname:matrix**axis1:***Type:User-definedAxis***Name:which***Values:onetwo#Createanothermatrix-configurationproject**projectname:matrix-copier**axis1:***Type:User-definedAxis***Name:which***Values:onetwo#ConfigureCopyArtifactinmatrix-copierlikethis:**Projectname:matrix/which=$
\
{which
\
}#UpgradeCopyArtifactto1.26orlater.#Runabuildformatrix-copier.#ConfigurationofCopyArtifactinmatrix-copierisupgradedlikethis:**Projectname:matrix**Parameterfilters:which=$
\
{which
\
}
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] [copyartifact] (JENKINS-19057) ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
ikedam
updated JENKINS-19057
ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
Change By:
ikedam
(03/Aug/13 8:44 AM)
Description:
#InstallCopyArtifact1.25.#Createamulti-configurationprojectlikethis:**projectname:matrix**axis1:***Type:User-definedAxis***Name:which***Values:onetwo#Createanothermatrix-configurationproject**projectname:matrix-copier**axis1:***Type:User-definedAxis***Name:which***Values:onetwo#ConfigureCopyArtifactinmatrix-copierlikethis:**Projectname:matrix/which=${which}#UpgradeCopyArtifactto1.26orlater.#Runabuildformatrix-copier.#ConfigurationofCopyArtifactinmatrix-copierisupgradedlikethis:**Projectname:matrix**Parameterfilters:which=${which}
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] [plugin] (JENKINS-14087) ScriptTrigger plugin timer issue
Gregory Boissinot resolved JENKINS-14087 as Cannot Reproduce ScriptTrigger plugin timer issue Unfortenately, I can't reproduce it. It is OK in my environment. @wael for your previous issues, please could you test from ScriptTrigger 0.30. Change By: Gregory Boissinot (03/Aug/13 8:46 AM) Status: InProgress Resolved Resolution: CannotReproduce 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] [plugin] (JENKINS-14087) ScriptTrigger plugin timer issue
Gregory Boissinot edited a comment on JENKINS-14087 ScriptTrigger plugin timer issue Unfortunately, I can't reproduce it. It is OK in my environment. @wael for your previous issues, please could you test from ScriptTrigger 0.30. 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] [copyartifact] (JENKINS-19057) ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
ikedam
commented on JENKINS-19057
ProjectName with variables in CopyArtifact 1.26 is improperly upgraded.
This seems caused because CopyArtifact#upgradeIfNecessary cannot find a project "matrix/which=${which}".
This may be processed like this:
upgradeIfNecessary receives variables from perform.
Expand projectName with variables.
If a project named expanded projectName, consider projectName can be used as project. If not, projectName is considered contains project and parameter.
When onCopy, variables cannot be retrieved.
If projectName contains variables (that is, contains $), the configuration should not be upgraded.
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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Henry Huang created JENKINS-19058 ec2-plugin cannot add specified instance tags on launched spot instances Issue Type: Bug Assignee: Francis Upton Components: ec2, plugin Created: 03/Aug/13 11:09 AM Description: It is really urgent for me to choose the latest EC2 plugin (still not released) in testing. It seems that there are no latest commits since two months ago. I have configured the tags for my new spot instance request, like: Name: Name Value: Henry But after the spot instance launched, it seems no tags have been attached to this spot instance. Could you please fix it before the official release? Thanks Henry Environment: Jenkins 1.525, Amazon EC2 plugin v1.19-unreleased (last commit: #1e009adfa3) Project: Jenkins Labels: ec2 plugin tags instance spot Priority: Major Reporter: Henry Huang 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] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
kutzi updated JENKINS-15935 Cant build using maven 3.1.0 latest release candidate Change By: kutzi (03/Aug/13 11:13 AM) Labels: lts-candidate 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] [ec2] (JENKINS-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)
Henry Huang created JENKINS-19059 [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access) Issue Type: Improvement Assignee: Francis Upton Components: ec2, plugin Created: 03/Aug/13 11:24 AM Description: From help message in EC2Cloud Configuration, I need to let spot instance notify Jenkins master know this slave alive after it is available. As My AMI is based on CentOS, I cannot take the script it mentioned. Here is my understanding on the callback process. Jenkins Master does the spot instance request also with a default parameter in instance userdata, like: JENKINS_URL=http://1.1.1.1:8080/SLAVE_NAME=XXXUSER_DATA= Then the callback script will first download the "slave.jar" and use it to notify Jenkins Master know this slave alive: java -jar slave.jar -jnlpUrl http://1.1.1.1:8080/XXX/slave-agent.jnlp However, due to my Jenkins master deployed internally with no public access, so it makes Jenkins master considers this slave not ready. I also try to run these commands into an internal machine and wish Maser could let it go. But with 403 forbidden response. Could you please help me on this issue? I feel this deployment is also quite common. Thanks Henry Environment: Jenkins 1.525, Amazon EC2 plugin v1.19-unreleased (last commit: #1e009adfa3) Project: Jenkins Labels: master spot instance ec2-plugin internal notification Priority: Major Reporter: Henry Huang 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] [ec2] (JENKINS-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)
Henry Huang updated JENKINS-19059 [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access) Change By: Henry Huang (03/Aug/13 11:28 AM) Description: From the helpmessageinEC2Cloud Configuration configuration ,Ineedtoletspotinstancenotify the Jenkinsmaster know that thisslave aliveafterit isavailable.As My my AMIisbasedonCentOS,Icannottakethescript directlyas itmentioned. Here SoIhavegonethroughthescriptandhere ismyunderstandingonthecallbackprocess. Jenkins Master master doesthespot - instancerequestalsowithadefaultparameterininstanceuserdata,like:JENKINS_URL=http://1.1.1.1:8080/SLAVE_NAME=XXXUSER_DATA=Thenthecallbackscriptwillfirstdownloadtheslave.jaranduseittonotifyJenkinsMaster know that thisslave is alive:java-jarslave.jar-jnlpUrlhttp://1.1.1.1:8080/XXX/slave-agent.jnlpHowever,duetomyJenkinsmasterdeployedinternallywithnopublicaccess, soitmakes Jenkinsmaster considers willkeepconsidering thisslavenotready.Ialsotrytorunthesecommands into on aninternalmachineandwish Maser Master couldletitgo.But with onlygetthe 403forbidden response.Couldyoupleasehelpmeonthisissue?Ifeelthisdeploymentisalsoquitecommon then .ThanksHenry 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] [maven] (JENKINS-15935) Can't build using maven 3.1.0
kutzi updated JENKINS-15935 Cant build using maven 3.1.0 Change By: kutzi (03/Aug/13 11:29 AM) Summary: Cantbuildusingmaven3.1.0 latestreleasecandidate 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] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
SCM/JIRA link daemon commented on JENKINS-17961 URLTrigger does not poll when URL starts with environment variable Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java src/main/java/org/jenkinsci/plugins/urltrigger/URLTriggerEntry.java src/main/java/org/jenkinsci/plugins/urltrigger/URLTriggerResolvedEntry.java http://jenkins-ci.org/commit/urltrigger-plugin/3b58375adc94fb288f3697bfc85f86aab06d08b3 Log: Fix JENKINS-17961 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] [urltrigger] (JENKINS-17961) URLTrigger does not poll when URL starts with environment variable
Gregory Boissinot resolved JENKINS-17961 as Fixed URLTrigger does not poll when URL starts with environment variable Change By: Gregory Boissinot (03/Aug/13 12:01 PM) Status: Open Resolved 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] [core] (JENKINS-19004) Channel's executorService's pool should have a name
kutzi commented on JENKINS-19004 Channels executorServices pool should have a name I think, I can answer my previously comment by myself: Limiting the number of the threads in the thread pool - no matter how high the number of threads would be - would always bear the danger of deadlocks 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] [extra-columns] (JENKINS-19021) Build Description column should reflect previous build while another is in process
SCM/JIRA link daemon resolved JENKINS-19021 as Fixed Build Description column should reflect previous build while another is in process Change By: SCM/JIRA link daemon (03/Aug/13 4:24 PM) Status: Open Resolved 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] [extra-columns] (JENKINS-19021) Build Description column should reflect previous build while another is in process
SCM/JIRA link daemon commented on JENKINS-19021 Build Description column should reflect previous build while another is in process Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/BuildDescriptionColumn.java http://jenkins-ci.org/commit/extra-columns-plugin/cbaaef99711c8d0a8072021ad2648d16043055f0 Log: FIXED JENKINS-19021 - Build Description column should reflect previous build while another is in process 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] [android-emulator] (JENKINS-18970) PatternSyntaxException in Windows when updating project files
Aitor Mendaza assigned JENKINS-18970 to Aitor Mendaza PatternSyntaxException in Windows when updating project files Change By: Aitor Mendaza (03/Aug/13 5:23 PM) Assignee: ChristopherOrr AitorMendaza 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] [android-emulator] (JENKINS-18970) PatternSyntaxException in Windows when updating project files
Aitor Mendaza started work on JENKINS-18970 PatternSyntaxException in Windows when updating project files Change By: Aitor Mendaza (03/Aug/13 5:23 PM) Status: Open InProgress 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] [android-emulator] (JENKINS-18970) PatternSyntaxException in Windows when updating project files
Aitor Mendaza commented on JENKINS-18970 PatternSyntaxException in Windows when updating project files I have added some code to fix the bug. I have send a pull request to be integrated in the main branch: https://github.com/jenkinsci/android-emulator-plugin/pull/26 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] [accurev] (JENKINS-13406) Accurev plugin changeLog not showing parent stream files modified while using accurev workspace.
Ray Munian commented on JENKINS-13406 Accurev plugin changeLog not showing parent stream files modified while using accurev workspace. Changeset: 0a2cbac806ff1e4f636310479f1fa470fbf3682f Author:Raymond Munian Date: 2013-08-03 13:22 Message: Fix JENKINS-13406 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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Adam Irr commented on JENKINS-19058 ec2-plugin cannot add specified instance tags on launched spot instances Some more information about why this is happening. Spot Instance Requests should be getting the tags assigned. The problem is that the tags do not then get passed on to the fulfilling instance. According to the AWS documentation this is the intended behavior (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts-spot-instances-request-tags.html). It seems we need to manually pass on the tags from the Spot Request to the actual instance. 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] [ec2] (JENKINS-19059) [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access)
Adam Irr commented on JENKINS-19059 [ec2-plugin] spot instance feature cannot be used when the master deployed internally (no public access) It sounds like your configuration is set up correctly. As you state, the issue is your non-public Jenkins master. Since jnlp requires the slave to connect to the master, it will not be possible for the instance to find the master and connect to it. Since currently the only way to launch Spot instances through the plugin is with jnlp, I don't think this will be easily fixable. The alternative is to give an option to launch the Spot instances in the same manner as On demand instance in which the Jenkins master connects to the slave. This would result in Jenkins polling EC2 frequently on the initial start up of a Spot instance to determine when there is a usable instance. Also if a persistent bid is used, and the Spot instance was terminated, the instance might eventually restart, but Jenkins would not know about it. 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Kanstantsin Shautsou commented on JENKINS-18686 Missing delete button for post build step I set de to default lang and see "delete" button. 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] [email-ext] (JENKINS-18686) Missing delete button for post build step
Kanstantsin Shautsou edited a comment on JENKINS-18686 Missing delete button for post build step I set de to default lang and see "delete" button. Try check http://url:8080/administrativeMonitor/OldData/manage 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] [doxygen] (JENKINS-17387) Doxygen Plugin fails with Statuscode 500
Kanstantsin Shautsou commented on JENKINS-17387 Doxygen Plugin fails with Statuscode 500 Do you want provide any other useful info? Doxygen configuration, plugin version, jenkins version?! 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] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe assigned JENKINS-9258 to Kohsuke Kawaguchi Remember me on this computer, still getting asked to log in after a few hours Assigning to Kohsuke, as active-directory lead. Change By: James Howe (03/Aug/13 7:12 PM) Assignee: KennethEndfinger KohsukeKawaguchi 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] [xunit] (JENKINS-16140) Clock on this slave is out of sync with the master
Kanstantsin Shautsou commented on JENKINS-16140 Clock on this slave is out of sync with the master It's the rule: always sync time. 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] [saferestart] (JENKINS-13908) Safe Restart plungin is throwing HTTP Status 500 on Jenkins 1.424.1.
Kanstantsin Shautsou commented on JENKINS-13908 Safe Restart plungin is throwing HTTP Status 500 on Jenkins 1.424.1. Is this issue actual? 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] [email-ext] (JENKINS-18905) A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build .
Kanstantsin Shautsou updated JENKINS-18905 A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build . Changing to email-ext. Looks like it's because of template. Change By: Kanstantsin Shautsou (03/Aug/13 7:25 PM) Component/s: email-ext Component/s: www 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] [email-ext] (JENKINS-18905) A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build .
Kanstantsin Shautsou updated JENKINS-18905 A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build . Change By: Kanstantsin Shautsou (03/Aug/13 7:26 PM) Assignee: AlexEarl 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] [email-ext] (JENKINS-18905) A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build .
Kanstantsin Shautsou commented on JENKINS-18905 A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build . Could you describe more? What triggers do you have in email-ext? How i can reproduce? What template is used? 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] [perforce] (JENKINS-16972) detects valid p4 output as authentication error
Kanstantsin Shautsou commented on JENKINS-16972 detects valid p4 output as authentication error Are you sure that this is not an error from p4 tools view? Did you set user/password correctly? 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] [perforce] (JENKINS-13907) Slave root directory changed, code on perforce is not synced.
Kanstantsin Shautsou commented on JENKINS-13907 Slave root directory changed, code on perforce is not synced. Always sync files. It's perforce architecture. 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] [android-emulator] (JENKINS-18970) PatternSyntaxException in Windows when updating project files
SCM/JIRA link daemon commented on JENKINS-18970 PatternSyntaxException in Windows when updating project files Code changed in jenkins User: Aitor Mendaza-Ormaza Path: src/main/java/hudson/plugins/android_emulator/util/Utils.java http://jenkins-ci.org/commit/android-emulator-plugin/378acf0718d7c3086dbbbac6cfb1f0fe5ca9022e Log: FIXED JENKINS-18970 Escape File.separator when used in a regex. 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] [android-emulator] (JENKINS-18970) PatternSyntaxException in Windows when updating project files
SCM/JIRA link daemon resolved JENKINS-18970 as Fixed PatternSyntaxException in Windows when updating project files Change By: SCM/JIRA link daemon (03/Aug/13 8:07 PM) Status: InProgress Resolved 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] [android-emulator] (JENKINS-18584) Install Android package task doesn't find aapt with newer SDK
SCM/JIRA link daemon commented on JENKINS-18584 Install Android package task doesnt find aapt with newer SDK Code changed in jenkins User: Steve Moyer Path: src/main/java/hudson/plugins/android_emulator/SdkInstallationException.java src/main/java/hudson/plugins/android_emulator/sdk/AndroidSdk.java src/main/java/hudson/plugins/android_emulator/sdk/DefaultToolLocator.java src/main/java/hudson/plugins/android_emulator/sdk/PlatformToolLocator.java src/main/java/hudson/plugins/android_emulator/sdk/Tool.java src/main/java/hudson/plugins/android_emulator/sdk/ToolLocator.java src/main/java/hudson/plugins/android_emulator/util/Utils.java http://jenkins-ci.org/commit/android-emulator-plugin/d49096f96884b9ac405c988afa32f467de750d82 Log: FIXED JENKINS-18584 Add support for build-tools so aapt can be located in newer SDKs. 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] [sounds] (JENKINS-13825) Sounds plugin configuration System command is empty
Denis Costa commented on JENKINS-13825 Sounds plugin configuration System command is empty Hi everyone. This issue is a big deal for me, so I'm willing to pay USD 5.00 for it. This offer is registered on FreedomSponsors (http://www.freedomsponsors.org/core/issue/315/sounds-plugin-configuration-system-command-is-empty). If you solve it (according to the acceptance criteria described there), please register on FreedomSponsors and mark it as resolved there I'll then check it out and gladly pay up! Oh, and if anyone else also wants throw in a few bucks on this, you should check out FreedomSponsors! 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] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
SCM/JIRA link daemon commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Code changed in jenkins User: Gregory Boissinot Path: src/main/java/com/thalesgroup/hudson/plugins/xunit/service/XUnitTransformer.java src/main/java/org/jenkinsci/plugins/xunit/SkipTestException.java src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/3d5fcf4abefbd70d965d2a01301e8f00cc7f4d4e Log: Fix JENKINS-18443 Compare: https://github.com/jenkinsci/xunit-plugin/compare/4a9dd4c67e95...3d5fcf4abefb 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] [buildresult-trigger] (JENKINS-18888) Add AND of build results instead of OR
Gregory Boissinot updated JENKINS-1 Add AND of build results instead of OR Change By: Gregory Boissinot (03/Aug/13 9:47 PM) Component/s: buildresult-trigger Component/s: buildresulttrigger 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] [crowd2] (JENKINS-17712) authentication by token with crowd2 plugin
Tim Snyder commented on JENKINS-17712 authentication by token with crowd2 plugin I think that I'm running into this too. I am trying to follow the examples on https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients. It works if I use my actual password for the password but if I try to use the API token that I found on my user configuration screen: The API token is available in your personal configuration page. Click your name on the top right corner on every page, then click "Configure" to see your API token. (The URL $root/me/configure is a good shortcut.) You can also change your API token from here. I get: Application name and/or password are not valid.; nested exception is com.atlassian.crowd.exception.InvalidAuthenticationException: Account with name tsnyder failed to authenticate. Is the API-token based authentication supposed to work with the Crowd2 plugin v1.5? 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] [buildresult-trigger] (JENKINS-18888) Add AND of build results instead of OR
SCM/JIRA link daemon commented on JENKINS-1 Add AND of build results instead of OR Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/xtrigger/AbstractTriggerByFullContext.java http://jenkins-ci.org/commit/xtrigger-lib/9833c11e062edad8998577d9506d6168cbf122cd Log: Fix JENKINS-1 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] [ec2] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
SCM/JIRA link daemon commented on JENKINS-18854 EC2 Plugin unable to connect to Eucalyptus 3.x Code changed in jenkins User: colbydyess Path: src/main/java/hudson/plugins/ec2/Eucalyptus.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/Eucalyptus/config-entries.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly http://jenkins-ci.org/commit/ec2-plugin/ecbe47f08826dd0dc8bd5e34ce8d3c8506ce44f1 Log: JENKINS-18854 - fixed Eucalyptus connectivity support 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] [ec2] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
SCM/JIRA link daemon commented on JENKINS-18854 EC2 Plugin unable to connect to Eucalyptus 3.x Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/Eucalyptus.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/Eucalyptus/config-entries.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly http://jenkins-ci.org/commit/ec2-plugin/98a36f1f251220869c0de90080710d3baa835ee9 Log: Merge pull request #58 from ColbyDyess/master JENKINS-18854 Compare: https://github.com/jenkinsci/ec2-plugin/compare/238903d22b76...98a36f1f2512 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] [ec2] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x
SCM/JIRA link daemon commented on JENKINS-18854 EC2 Plugin unable to connect to Eucalyptus 3.x Code changed in jenkins User: colbydyess Path: src/main/java/hudson/plugins/ec2/Eucalyptus.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/Eucalyptus/config-entries.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly http://jenkins-ci.org/commit/ec2-plugin/b55add0411a65b7a8c29c71c8b415c05c31aff41 Log: JENKINS-18854 - fixed Eucalyptus connectivity support 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] [core] (JENKINS-13908) Safe Restart plungin is throwing HTTP Status 500 on Jenkins 1.424.1.
sogabe updated JENKINS-13908 Safe Restart plungin is throwing HTTP Status 500 on Jenkins 1.424.1. SafeRestart Plugin only invoke core feature. Change By: sogabe (04/Aug/13 1:48 AM) Component/s: core Component/s: saferestart 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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Adam Irr assigned JENKINS-19058 to Adam Irr ec2-plugin cannot add specified instance tags on launched spot instances Change By: Adam Irr (04/Aug/13 3:08 AM) Assignee: FrancisUpton AdamIrr 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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
SCM/JIRA link daemon commented on JENKINS-19058 ec2-plugin cannot add specified instance tags on launched spot instances Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2ComputerListener.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java http://jenkins-ci.org/commit/ec2-plugin/6a374e309c229f1b3227791dea9c088eadb088db Log: Merge pull request #61 from aji9861/master JENKINS-19058 Fix cannot add tags to Spot Instances Compare: https://github.com/jenkinsci/ec2-plugin/compare/98a36f1f2512...6a374e309c22 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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
SCM/JIRA link daemon commented on JENKINS-19058 ec2-plugin cannot add specified instance tags on launched spot instances Code changed in jenkins User: Adam I Path: src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2ComputerListener.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java http://jenkins-ci.org/commit/ec2-plugin/f6d54a7948b171d093b02a7def4141d8b2716494 Log: JENKINS-19058 Fix cannot add tags to Spot Instances Add a ComputerListener so that we can take action when a slave is connected. This allows us to be notified when a Spot instance is connected and add the Spot Request's tags to its instance. 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] [core] (JENKINS-14264) Breadcrumb: the link to the lastBuild console is missing in the popup for a some jobs
mike bayer commented on JENKINS-14264 Breadcrumb: the link to the lastBuild console is missing in the popup for a some jobs this issue has driven me completely mad for months, and I just identified tonight that it is in fact two different "classes" of console output, based on the size of the log, and then from that "class" you get two entirely different UX treatments - the presence or lack of a "breadcrumb" link to the console output (why is the contextual popup called a "breadcrumb?" not really a breadcrumb...), as well as either "console output ... view as plain text" on the right for small logs or "console output raw" for large logs when you view the build itself. evernat seems to have identified this size as 200K, sounds about right - why isn't this hardcoded number configurable or documented anywhere ?why two entirely different sets of logic kicking in? why can't jenkins pay for all the psychiatric meds this issue has caused me? so many questions thanks for listening. 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] [ec2] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Adam Irr resolved JENKINS-19058 as Fixed ec2-plugin cannot add specified instance tags on launched spot instances When you get a chance let us know if you are still seeing this issue with the latest commit. Change By: Adam Irr (04/Aug/13 5:20 AM) Status: Open Resolved 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.
