[JIRA] [jira-plugin] (JENKINS-17156) If Updater fails to update due to missing permission, it crashes and never flushes the comment queue
Stephan Krull commented on JENKINS-17156 If Updater fails to update due to missing permission, it crashes and never flushes the comment queue see https://github.com/jenkinsci/jira-plugin/pull/50 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/d/optout.
[JIRA] [jira-plugin] (JENKINS-13500) Jira plugin post integrated in comment on every build
Stephan Krull commented on JENKINS-13500 Jira plugin post integrated in comment on every build This bug is considered in https://github.com/jenkinsci/jira-plugin/pull/50 and definitily a duplicate of JENKINS-17156 (hence should be 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/d/optout.
[JIRA] [core] (JENKINS-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull
edited a comment on JENKINS-21589
Unresolvable (environment) variables lead to failing maven builds
The scenario described here does not fail with maven-plugin version 2.7 on Jenkins LTS 1.565.3 anymore.
Although the plugin is able to resolve the global environment variable key while running (see log excerpt below) the output of the "resolved" maven command line still shows the placeholder ("${VAL_UE}")
Current scenario:
global environment variable: MAVEN_VAR_TEST=-Dclean.skip=ยง{VAL_UE}
maven job with simple pom, no clean-plugin config
job parameter boolean: VAL_UE
running maven goal: "clean ${MAVEN_VAR_TEST}"
build log with VAL_UE=true (excerpt):
...
Parsing POMs
maven31-agent.jar already up to date
maven31-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
...
===[JENKINS REMOTING CAPACITY]===channel started
Executing Maven: -B -f SLAVE_HOME/workspace/maventest/pom.xml clean -Dclean.skip=${VAL_UE}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Maven Project 4.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ maven.project ---
[INFO] Clean is skipped.
[JENKINS] Archiving disabled
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[JENKINS] Archiving disabled[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1.000 s
[INFO] Finished at: 2014-10-15T13:56:47+02:00
[INFO] Final Memory: 7M/107M
[INFO]
build log with VAL_UE=false (excerpt):
...
Parsing POMs
maven31-agent.jar already up to date
maven31-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
...
===[JENKINS REMOTING CAPACITY]===channel started
Executing Maven: -B -f /home/cc/jenkins-slave/workspace/maventest/pom.xml clean -Dclean.skip=${VAL_UE}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Maven Project 4.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ maven.project ---
[JENKINS] Archiving disabled
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[JENKINS] Archiving disabled[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.969 s
[INFO] Finished at: 2014-10-15T14:07:34+02:00
[INFO] Final Memory: 6M/106M
[INFO]
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/d/optout.
[JIRA] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible I checked your snapshot HPI with Jenkins 1.565.1, fresh installation. Same as before, installing ownership plugin, checking "Require Configure rights" and "Setup after creation" in system configuration, security configuration with Jenkins internal, registering a test user, logging in, creating a job. Managing ownership of a job works with that environment, but there is another bug: Unable to render embedded object: File (own_fix_check_1.png) not found. Snapshot1: system configuration for ownership plugin - expecting to give ownership of a newly created job to the current loggin in user Unable to render embedded object: File (own_fix_check2.png) not found. Snapshot2: new created job summary view; has been created by loggin in user "stephan (test)" Unable to render embedded object: File (own_fix_check3.png) not found. Snapshot3: view of system configuration for ownership plugin As you can see the system configuration does not respect checking of "Setup after creation", this could be the reason for the unowned new job (see Snapshot2). 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/d/optout.
[JIRA] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
Stephan Krull updated JENKINS-24475 Managing ownership not possible Change By: Stephan Krull (30/Sep/14 6:40 AM) Attachment: own_fix_check_1.png Attachment: own_fix_check2.png Attachment: own_fix_check3.png 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/d/optout.
[JIRA] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
Stephan Krull edited a comment on JENKINS-24475 Managing ownership not possible I checked your snapshot HPI with Jenkins 1.565.1, fresh installation. Same as before, installing ownership plugin, checking "Require Configure rights" and "Setup after creation" in system configuration, security configuration with Jenkins internal, registering a test user, logging in, creating a job. Managing ownership of a job works with that environment, but there is another bug: Snapshot1: system configuration for ownership plugin - expecting to give ownership of a newly created job to the current loggin in user Snapshot2: new created job summary view; has been created by loggin in user "stephan (test)" Snapshot3: view of system configuration for ownership plugin As you can see the system configuration does not respect checking of "Setup after creation", this could be the reason for the unowned new job (see Snapshot2). 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/d/optout.
[JIRA] [ownership-plugin] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible updated to ownership 0.5.1; changed email resolver in system configuration to ldap; created job and tried to manage ownership - this is the favored use case in production mode - everything works fine. thank you! 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull updated JENKINS-24475 Managing ownership not possible Change By: Stephan Krull (26/Sep/14 2:15 PM) Attachment: job_summary.png Attachment: logged_in.png 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible I saw that you released version 0.5. So I did another test today. Jenkins 1.565.1 (I know there is a 1.565.2 meanwhile); JDK6 on Ubuntu 10.04.4 LTS; running JDK6_HOME/bin/java -jar jenkins.war with a clean USER_HOME/.jenkins/ installed ownership plugin 0.4; system configuration: setting global ownership options "Setup after creation" and "Require Configure rights" to true global security configuration: Jenkins internal user management registered a user logged in as the user created a job after creation the user is the owner of that job trying to "manage owners" I get the redirect that is described in this bug While resetting JENKINS_DATA_HOME and installing version 0.5 instead of 0.4 this bug cannot be reproduced. I just acknowledged another thing with 0.5: When creating a new job, as a registered and logged in user, after confirmation of the job form the user is not owner of that plugin see here: 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull edited a comment on JENKINS-24475 Managing ownership not possible I saw that you released version 0.5. So I did another test today. Jenkins 1.565.1 (I know there is a 1.565.2 meanwhile); JDK6 on Ubuntu 10.04.4 LTS; running JDK6_HOME/bin/java -jar jenkins.war with a clean USER_HOME/.jenkins/ installed ownership plugin 0.4; system configuration: setting global ownership options "Setup after creation" and "Require Configure rights" to true global security configuration: Jenkins internal user management registered a user logged in as the user created a job after creation the user is the owner of that job trying to "manage owners" I get the redirect that is described in this bug While resetting JENKINS_DATA_HOME and installing version 0.5 instead of 0.4 this bug cannot be reproduced. I just acknowledged another thing with 0.5: When creating a new job, as a registered and logged in user, after confirmation of the job form the user is not owner of that plugin see here: In (the now working) dialog of "manage owners" the plugin knows the owner very well: see here the moment I wanted to take the screenshot the bug reoccured. Kind of frustrating. I hope you can reproduce that. One thing I can confirm: If I uncheck the global option "Require Configure rights" the managing of ownership on a job is successful. 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/d/optout.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Stephan Krull commented on JENKINS-19142 Dont add jobs to a view Oleg Nenashev's workaround works perfect for me. This keeps me from insisting to the following detail: By closing JENKINS-19596 this issue is no longer treated as a bug but as an improvement. I disagree because in my understandig there should be differantiation between job and view. A view has to show objects that have been configured for that view. If there is a regex or a manually checked lists of jobs that belong to that view than no algorithm or automatic process should slip in this configuration (as is by creating a new job in that view). A newly created job should be included only in views whose configurations is appropriate. This definition makes this issue a bug. 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/d/optout.
[JIRA] [core] (JENKINS-19596) New job added when current view is on a regular expression view
Stephan Krull commented on JENKINS-19596 New job added when current view is on a regular _expression_ view Verify this is still a problem in LTS 1.565.2 and 1.577. We have a global entry view for all authenticated users showing just the most important jobs they need (we further encourage developers to foster their own views). I use a Regex together with job filters to achieve presentation of needed jobs. Unfortunately I have to delete new created jobs manually because they have been registered by magic. 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull updated JENKINS-24475 Managing ownership not possible Change By: Stephan Krull (29/Aug/14 12:17 PM) Attachment: installed_plugins.png 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible No change in JENKINS_URL. I tested with ownership-0.3 and get the same error. Responsibility for that error seems to be another component. Find attached the list of active plugins in my fresh Jenkins LTS 1.565.1 instance. Could you please once again try to reproduce the error? Thank you! 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull commented on JENKINS-24475 Managing ownership not possible I can reproduce that same error on: Jenkins 1.577 fresh instance (running with "java -jar jenkins.war") without updating all the bundled plugins installing ownership-0.4 configuring setup ownership when creating jobs configuring security and registering as a user creating a job and trying to manage ownership afterwards on firefox an ie Any ideas what can lead to the redirect? 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/d/optout.
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull created JENKINS-24475 Managing ownership not possible Issue Type: Bug Assignee: Oleg Nenashev Components: ownership Created: 28/Aug/14 10:34 AM Description: After upgraded to latest LTS and ownership plugin version I am no longer able to configure ownership of jobs and nodes. Trying to visit "JENKINS_URL/computer/NODENAME/ownership/manage-owners" or "JENKINS_URL/job/JOBNAME/ownership/manage-owners" I get redirected to i.e. "JENKINS_URL/login?from=%2Fjob%2FJOBNAME%2Fownership%2Fmanage-owners" although I am logged in already; session is kept alive. I tried with changing from "project based matrix access" to "all access to authenticated users" but same error. I tried with a clean jenkins instance (LTS 1.565.1), installing ownership plugin only; configured ownership to pin current user to created job; configured global security: all access to authenticated user, user self registration enabled; then registered myself, created a job. See myself as primary owner of the job. Taking the described action leads to the same error. Environment: Jenkins LTS 1.565.1; ownership plugin 0.4 without job-restrictions plugin and role-strategy plugin; global security settings: - user realm: LDAP - project based matrix access Project: Jenkins Priority: Blocker Reporter: Stephan Krull 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/d/optout.
[JIRA] [core] (JENKINS-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull
created JENKINS-21589
Unresolvable (environment) variables lead to failing maven builds
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
globalenv.png, mvnconf.png
Components:
core, maven
Created:
31/Jan/14 8:16 AM
Description:
The following scenario leads to failing builds because of faulty behaviour of Jenkins:
create a global environment variable:
create a job (maven or freestyle; did not test it on matrix)
configure maven: (enter the global env variable)
run the job
you get something like:
Modules changed, recalculating dependency graph
maven-agent.jar already up to date
classworlds.jar already up to date
maven-interceptor.jar already up to date
maven2.1-interceptor.jar already up to date
[amavenjob] $ java -Xmx512m -XX:MaxPermSize=256m -cp PATH/jenkins-slave/maven-agent.jar:PATH/jenkins-slave/classworlds.jar hudson.maven.agent.Main PATH/maven/current PATH/jenkins-slave/slave.jar PATH/jenkins-slave/maven-interceptor.jar 40919 PATH/jenkins-slave/maven2.1-interceptor.jar
===[JENKINS REMOTING CAPACITY]===channel started
log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Executing Maven: -B -f PATH/jenkins-slave/workspace/amavenjob/pom.xml clean install ${JOB_MVN_PARAM}
[INFO] Scanning for projects...
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Invalid task '${JOB_MVN_PARAM}': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jan 31 09:12:40 CET 2014
[INFO] Final Memory: 3M/59M
[INFO]
channel stopped
Finished: FAILURE
Environment:
Jenkins 1.532.1 (LTS); JRE 7; Unix Daemon
maven-plugin 2.0.3
Project:
Jenkins
Priority:
Major
Reporter:
Stephan Krull
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-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull
commented on JENKINS-21589
Unresolvable (environment) variables lead to failing maven builds
Maven is not able to ignore a placeholder in its commandline. Jenkins has to do that just before calling maven.
Maybe other tools are affected too.
I propose to filter the maven goals before committing them to a Builder.
For a private hotfix I used this method:
private ListString getListWithoutUnresolvableVariables(ArgumentListBuilder alb)
{
ListString result = new LinkedListString();
// pattern taken from hudson.Util.VARIABLE
final Pattern varPattern = Pattern.compile("\\$([A-Za-z0-9_]+|\\{[A-Za-z0-9_.]+\\}|\\$)");
for( String entry : alb.toList())
{
Matcher m = varPattern.matcher(entry);
final String intern = m.replaceAll("").trim();
if (0 intern.length())
{
result.add(intern);
}
}
return result;
}
to modify the calculated hudson.util.ArgumentListBuilder in hudson.maven.MavenModuleSetBuild.MavenModuleSetBuildExecution.doRun(BuildListener). This works well for Maven jobs but not for freestyle jobs.
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-21589) Unresolvable (environment) variables lead to failing maven builds
Stephan Krull commented on JENKINS-21589 Unresolvable (environment) variables lead to failing maven builds Maybe someone is interested in the usecase of the scenario described above: We are using homogeneous maven commands for all maven jobs that are based on company standard. Additionally these jobs are created from a template where the global environment variables are configured. Now and then a developer needs additional parameters added to the standard maven command. With Hudson I defined a placeholder environment variable without a value, the developer did an overwrite of this variable on his maven job. With Jenkins overwriting an environment variable does not work. I deleted the placeholder from the global environments an got the error message that is base to this issue because the placeholders are not configured in every job. 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] [jobconfighistory] (JENKINS-21406) Show Config Versions in Diff View
Stephan Krull commented on JENKINS-21406 Show Config Versions in Diff View Thank you very much, looking forward to the release of 2.6! 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-21035) Last modification of job configuration column
Stephan Krull started work on JENKINS-21035 Last modification of job configuration column Change By: Stephan Krull (17/Dec/13 9:56 AM) 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] [extra-columns] (JENKINS-21035) Last modification of job configuration column
Stephan Krull assigned JENKINS-21035 to Fred G Last modification of job configuration column @Fred G: please review and pull request: https://github.com/jenkinsci/extra-columns-plugin/pull/3 Change By: Stephan Krull (17/Dec/13 9:58 AM) Assignee: StephanKrull FredG 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-21035) Last modification of job configuration column
Stephan Krull edited a comment on JENKINS-21035 Last modification of job configuration column @Fred G: please review and pull request: https://github.com/jenkinsci/extra-columns-plugin/pull/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] [extra-columns] (JENKINS-21037) Slave or label restriction of a job
Stephan Krull created JENKINS-21037 Slave or label restriction of a job Issue Type: New Feature Assignee: Stephan Krull Attachments: slaveOrLabel.png Components: extra-columns Created: 17/Dec/13 10:40 AM Description: View column that shows build processor or build processor label restriction of a job. Project: Jenkins Priority: Major Reporter: Stephan Krull 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-21037) Slave or label restriction of a job
Stephan Krull assigned JENKINS-21037 to Fred G Slave or label restriction of a job @Fred G: please review and pull request: https://github.com/jenkinsci/extra-columns-plugin/pull/6 Change By: Stephan Krull (17/Dec/13 11:00 AM) Assignee: StephanKrull FredG 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.
