Cool, I'll take a look then :-) Thanks
On Tue, Aug 19, 2014 at 3:32 PM, Jesse Glick wrote:
> Added classpath support finally in 1.5.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receivi
Added classpath support finally in 1.5.
--
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, visit
I get the same problem. I don't have access to the logs. I think
Kohsuke will have to help...
On Tue, Aug 19, 2014 at 1:55 PM, Patrik Boström wrote:
> Can someone please help me with this?
>
> Regards
> Patrik Boström
>
>
> On Tuesday, 1 July 2014 22:26:52 UTC+2, Patrik Boström wrote:
>>
>> Hi,
>
Can someone please help me with this?
Regards
Patrik Boström
On Tuesday, 1 July 2014 22:26:52 UTC+2, Patrik Boström wrote:
>
> Hi,
>
> I have problems editing the Confluence page
> https://wiki.jenkins-ci.org/display/JENKINS/Delivery+Pipeline+Plugin, I
> just get "An error occured while trying
I don't think that the token macro stuff should be integrated into the
core. There are other ways of generating parameter values to pass along, I
believe the EnvInject plugin is the way to go. Integrating Token Macro into
core is not going to happen.
On Tue, Aug 19, 2014 at 8:36 AM, Paul Sokolovs
On Tue, 19 Aug 2014 07:05:40 -0700
Slide wrote:
> You are correct. Token macro expansion only happens if it is
> explicitly used in the code that uses the value on the server side.
> Most fields in Jenkins don't do token macro expansion. The EnvInject
> may allow you to do something like what you
Hey,
So as I mentioned earlier (and I kinda mentioned on the users mailing
list a few weeks ago), I had starting working on basically the same plugin.
I finally got some time to finish the first version and do lots of
testing with it (apparently the Google Play API has a "daily save
quota",
Hi there,
On 14/08/14 09:41, David Hamm wrote:
I agree to most of the points you wrote. but please take a look at the
current version of the plugin. it is currently 0.1.0, which means i'll
work further on the plugin and improve it step by step.
oauth is definitely one of the next features that
So, let's keep it as "play-autotest-plugin".
The plugin was tested (also with master/slave config) and I'm confident
it's ready to ship...
What to do next? Should I create a Pull Request?
On Sunday, August 17, 2014 2:10:54 PM UTC+2, Christopher wrote:
>
> Wasn't the whole reason to rename the
You are correct. Token macro expansion only happens if it is explicitly
used in the code that uses the value on the server side. Most fields in
Jenkins don't do token macro expansion. The EnvInject may allow you to do
something like what you want.
On Tue, Aug 19, 2014 at 6:19 AM, Paul Sokolovsky
Hello,
I'm trying to take a value as produced by some plugin's token macro
support and inject it into job's build, so eventually it is available
in slave's environment to a shell script.
After some thinking, an obvious way to achieve that seems to make a job
parametrized, and just set its default
hi there,
is there any progress on hosting this plugin?
is there anything i need to do in order to get this plugin hostet?
kind regards
david
Am Mittwoch, 13. August 2014 20:27:35 UTC+2 schrieb David Hamm:
>
> Hi,
>
> i created a google play publisher plugin for android app.
> the project is loc
Hello,
Thank you for your help - I didn't know about the separate mailing list, I
will use it from now on.
Thanks again,
Costin.
_
Costin Caraivan
On Tue, Aug 19, 2014 at 10:51 AM, Daniel Spilker
wrote:
> Hi,
>
> you can use the following lines in your Job DSL script to get a map
*JENKINS CI FESTIVAL!*
*Thursday August 21st* we're hosting a Code Camp for developers
*Friday August 22nd *the Scandinavian Jenkins CI Community will meet at a
conference
Come meet with your Jenkins CI peers for networking and knowledge sharing.
The Code Camp will include an introduction to
Hi,
you can use the following lines in your Job DSL script to get a mapping of
settings names to IDs.
import jenkins.model.Jenkins
Jenkins jenkins = Jenkins.getInstance()
def mavenSettingsConfigProvider =
jenkins.getExtensionList("org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig\$Ma
15 matches
Mail list logo
