Hi,
I have been trying to get this patch in for quite sometime now.
https://github.com/jenkinsci/android-emulator-plugin/pull/23
It addresses a major issue (
https://issues.jenkins-ci.org/browse/JENKINS-15928) on the android-emulator
plugin for jenkins
Its a pretty straightforward fix. I have
Dear. Jenkins Administrator
I am sending this e-mail because I don't know how to withdraw in
jenkins-ci.org
I joined two ID(snazzy79, blogfein) in jenkins-ci.org.
Of these, I only want to use blogfein
Therefore, I wish you drop the account snazzy79
And I wish you changes ID in the following
Hi,
I just got an email explaining the new pull request policy.
I found it very nice. It really favors contributions.
So, I would like to get commit rights for the job-import-plugin repository to
include this small contribution:
https://github.com/jenkinsci/job-import-plugin/pull/2
Thank you,
Hi Christophe, your commit rights are all set.
Please consider adding a unit test before you merge your changes.
Ulli
Am 17.07.2013 um 10:00 schrieb Christophe Demarey christophe.dema...@inria.fr:
Hi,
I just got an email explaining the new pull request policy.
I found it very nice. It
Hello,
some time ago, I made a pull-request (157) for the git-plugin to fix bug
#JENKINS-18328:
https://github.com/jenkinsci/git-plugin/pull/157
https://issues.jenkins-ci.org/browse/JENKINS-18328
Now I was referred to http://jenkins-ci.org/pull-request-greeting and
learned that I formatted the
Hi Folks,
Due to some non backward compat changes in maven core 3.1.x, this
doesn't work anymore.
Yes I know some of you (at least I know one!) think this need to be rewrite.
BTW I don't have enough time for the moment to fully rewrite this (but
some ideas :-))
So in order to take care of users,
On 17 July 2013 10:23, Olivier Lamy oliver.l...@gmail.com wrote:
Hi Folks,
Due to some non backward compat changes in maven core 3.1.x, this
doesn't work anymore.
Yes I know some of you (at least I know one!) think this need to be
rewrite.
(I know one == me)
I don't think is needs to be
Hello,
On a slightly different but related topic, I was thinking it could be
worth having a Builder class to supercede hudson.tasks.Maven (in
core), but to store that builder in the current maven-plugin. That
would avoid duplicating some logic to the builder sitting in core just
because it
I would favour moving the Maven stuff from core out into a maven-core
plugin. My plans will need some of the stuff in core but *none* of the
stuff in the current maven plugin, so I would be against moving the stuff
from core to the current maven plugin.
On 17 July 2013 10:51, Vincent Latombe
Three weeks ago I've made hosting request for my plugin *shared-workspace*:
https://groups.google.com/forum/#!topic/jenkinsci-dev/cYLWyVMJUe0
And there is no any feedback. Should I just continue to wait, or something
wrong in my request?
I've made maintainer-info addition in *pom.xml* (like in
In one of my pull requests (
https://github.com/jenkinsci/gradle-plugin/pull/18), I've changed the
parent pom version from 1.409 to 1.427 in order to allow compiling with
OpenJDK. I'm assuming this means that the lowest Jenkins version supported
then becomes 1.427.
Does anyone have any objections
Hi,
I can see releases 1.3 of maven-interceptors but no tags in the git repository?
And this is the current version used by the core.
So what's wrong there?
Thanks,
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
--
You received this
I have written a test that causes the copy artifact plugin issue as
described in JENKINS-14900. This has prevented us from upgrading from
Jenkins 1.455, and it would be great to get the test landed so there's more
visibility to the issue.
Pull request:
Plugin compiled, runned and used on my device
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options,
https://github.com/jenkinsci/cpptest-plugin
Le mercredi 17 juillet 2013 14:36:50 UTC+2, Aurélien Hébert a écrit :
Plugin compiled, runned and used on my device
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this
Hi -
It looks like this plugin has been dormant; I realized when I submitted a pull
request https://github.com/jenkinsci/shelve-project-plugin-plugin/pull/2that
there was already a pull request for a different
feature https://github.com/jenkinsci/shelve-project-plugin-plugin/pull/1.
I'd love
Sounds good, except for readability. As a unaware user, I wouldn't
understand why there are two maven plugins for 'apparently' the same
features.
Maybe some wording like Maven builder plugin, and Maven project type
plugin would make it clearer.
Vincent
2013/7/17 Stephen Connolly
On 07/17/2013 05:23 AM, Olivier Lamy wrote:
Due to some non backward compat changes in maven core 3.1.x, this doesn't work
anymore.
Do you mean that the current plugin cannot be used to run a Maven 3.1.0+ tool? That is certainly unfortunate; I guess that means that there must be a third Maven
Hello Mr.Kohsuke,
Hats off for giving us Jenkins. I am thrilled by its capabilities.
My problem is that I am creating a job programmatically using create-job CLI
command. The job configuration will have password fields (for RTC, TFS,
Tomcat, etc). After the job gets created, the passwords were
Hi All.
I can't seem to get a radioBlock to persist when used for a Ruby plugin.
Does anyone have any experience with this?
Thanks, Matt.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving
On 07/17/2013 04:51 AM, Olaf Mandel wrote:
Can the commit still be used or should I make a new commit and pull request?
The commit can still be used. I just updated the title of the pull request to (1) be meaningful; (2) use the magic wording, since the title of the PR is used by default
for
On 07/17/2013 04:26 AM, Ulli Hafner wrote:
Hi Christophe, your commit rights are all set.
And if you are now the maintainer of this plugin, please consider merging #1 or
#3.
--
You received this message because you are subscribed to the Google Groups Jenkins
Developers group.
To unsubscribe
Done.
You will have to change the pom.xml to have that reflected in the wiki page.
On Wed, Jul 17, 2013 at 12:52 AM, JEE HYOUNG YOO snazzy7...@gmail.comwrote:
Dear. Jenkins Administrator
I am sending this e-mail because I don't know how to withdraw in
jenkins-ci.org
I joined two
In the plugin I'm working on, I need to present a list of choices to the user.
The user will be able to select one or more of them (thus checkboxes would be
appropriate, not radio buttons). Most likely I'll store the data in a
ListString or something similar.
The tricky part is that the list
Hello Mr.Kohsuke,
Hats off for giving us Jenkins. I am thrilled by its capabilities.
My problem is that I am creating a job programmatically using create-job
CLI command. The job configuration will have password fields (for RTC, TFS,
Tomcat, etc). After the job gets created, the passwords
Hello,
I'm currently working on a high availability(active-active) plugin for
Jenkins, and right now I'm trying to retrieve the parameters of a job
before it has been put into the queue.
I've tried all the getters available, i.e. project.getProperties,
project.getAllProperties,
Done.
Welcome aboard!
Ulli
Am 17.07.2013 um 15:10 schrieb Ben Patterson patterson@gmail.com:
Hi -
It looks like this plugin has been dormant; I realized when I submitted a
pull request that there was already a pull request for a different feature.
I'd love to finish mine off and
Does the Queue.task passed into QueueDecisionHandler.shouldSchedule() have
the info you need?
http://javadoc.jenkins-ci.org/hudson/model/Queue.QueueDecisionHandler.html#shouldSchedule(hudson.model.Queue.Task,
java.util.List)
On Wed, Jul 17, 2013 at 7:53 AM, Daniel Olausson
Done:
https://github.com/jenkinsci/shared-workspace-plugin
Welcome aboard!
Can you please add a wiki page that describes your plug-in?
Ulli
Am 17.07.2013 um 12:41 schrieb Sapone mylniko...@gmail.com:
Three weeks ago I've made hosting request for my plugin shared-workspace:
RunListenerRun {
public void onFinalized(Run r) {
r.getExecutor().getOwner().disconnect(null).get();
results in
ComputerLauncher::afterDisconnect
being called twice,
It also spews this to stderr:
WARNING: Channel reader thread: virtual.m21 for + virtual.m21 terminated
Am 17.07.2013 16:06, schrieb Jesse Glick:
On 07/17/2013 04:51 AM, Olaf Mandel wrote:
Can the commit still be used or should I make a new commit and
pull request?
The commit can still be used. I just updated the title of the pull
request to (1) be meaningful; (2) use the magic wording,
Hi,
I don't even see the corresponding commit, it looks like kohsuke did a
release with pushChanges=false, but forgot to push afterwards.
By the way, the tag for 1.2 (that you released) is missing as well
from the github repo [1]. It should be pointing to commit
Hi, I've made 2 pull requests which provide usefull features for me:
https://github.com/jenkinsci/buildtriggerbadge-plugin/pull/3
https://github.com/jenkinsci/redmine-plugin/pull/8
Some time ago for my previous pull I've requested for commit access, which
wasn't nessesary since my PR was merged
The data center that's housing one of our key servers (63.246.20.93) is
going to perform an infrastructure upgrade on July 21st between 02:00am UTC
to 08:00am
UTChttp://www.timeanddate.com/worldclock/fixedtime.html?msg=Jenkins+server+migrationiso=20130721T02ah=6
.
During this migration, multiple
Hi,
I created a pull request for junit-attachment plugin. Please somebody
review it.
https://github.com/jenkinsci/junit-attachments-plugin/pulls
Thank you very much.
Best regards,
Thomas Edwin Santosa
--
You received this message because you are subscribed to the Google Groups
Jenkins
35 matches
Mail list logo
