Domi,
are you planning an integration with the credentials plugin?
I hadn't considered it, but certainly I can see why it should. Mainly
I've just been exploring Jenkins plugin architecture, as this is my
first Jenkins plugin.
any idea when do cut the first release of this plugin?
I hope by the end of this week, as my time between jobs will be drawing
to a close. I think the minimum feature set for the initial release
should be liquibase execution and providing a list of changesets executed.
I also see there is not yet a component in the issue tracker - whats
your ID so we could create one for you?
My ID is "prospero238". Would love to start creating issues in Jira, if
only to formalize my own feature ideas.
Thanks for your interest and/or help!
~ Keith
On 05/03/2014 03:21 AM, [email protected] wrote:
Hi Keith,
are you planning an integration with the credentials plugin?
any idea when do cut the first release of this plugin?
I also see there is not yet a component in the issue tracker - whats
your ID so we could create one for you?
regards Domi
On 27 Apr 2014, at 17:51, Keith Collison <[email protected]
<mailto:[email protected]>> wrote:
That did the trick -- many thanks!
~ Keith
On Saturday, April 26, 2014 3:19:01 AM UTC-7, Ullrich Hafner wrote:
Sorry, due to the renaming of the repo the granted group has been
renamed too.
Can you please retry?
Am 25.04.2014 um 23:27 schrieb Keith Collison <[email protected]
<javascript:>>:
Perhaps I'm missing something, but I don't seem to be able to
commit to this repository:
remote: Permission to jenkinsci/liquibase-runner-plugin.git
denied to prospero238.
fatal: unable to access
'https://github.com/jenkinsci/liquibase-runner-plugin.git/':
<https://github.com/jenkinsci/liquibase-runner-plugin.git/%27:>
The requested URL returned error: 403
Please advise. Thank you in advance!
~ Keith
On Friday, April 25, 2014 11:40:20 AM UTC-7, Ullrich Hafner wrote:
Done: https://github.com/jenkinsci/liquibase-runner-plugin/
<https://github.com/jenkinsci/liquibase-runner-plugin/>
Am 25.04.2014 um 20:21 schrieb Keith Collison
<[email protected]>:
The repository was indeed created (I gather that this was
done perhaps by a bot).
However, the repository name seems a little funky, having
two dashes at the end of it ("liquibase-runner-plugin--").
While I'm sure this is merely cosmetic, if there's a way to
lop off those two dashes, I'd be pleased.
In addition (and no doubt more importantly), I don't seem
to be able to push to this repository. Running "git push"
yields:
Push failed: fatal: unable to access
'https://github.com/jenkinsci/liquibase-runner-plugin--.git/':
<https://github.com/jenkinsci/liquibase-runner-plugin--.git/%27:>
The requested URL returned error: 403
Let me know if I'm doing something bone-headed.
Thank you.
~ Keith
On Thursday, April 24, 2014 1:46:26 PM UTC-7, Dominik
Bartholdi wrote:
At least the repo exists - don't know if someone else
created it...
Am 24.04.2014 um 21:01 schrieb Ulli Hafner
<[email protected]>:
Ah, did it actually work? The bot didn't actually send
a response...
Am 24.04.2014 um 20:49 schrieb Dominik Bartholdi
<[email protected]>:
This seems already to be forked...
Domi
On 24.04.2014, at 00:10, Keith Collison
<[email protected]> wrote:
Greetings esteemed Jenkinists:
I have created a Jenkins Plugin and, per
instructions on the wiki, I am notifying this
mailing list as to its existence.
Details:
*Jenkins Plugin Name:* liquibase-runner
*Current Location:*
https://github.com/prospero238/liquibase-runner
<https://github.com/prospero238/liquibase-runner>
*Github User:* prospero238
*Jenkins-ci org account:* prospero238 (yes, same
name as my github user).
My understanding is that my current repo will be
forked. Further, I can looked forward to its
inclusion in the Cloudbees CI environment. I'll be
happy to create a wiki page once this is done (or,
if it standard to this beforehand, happy to do that
as well).
As this is my first plugin, I welcome comments and
suggestions about the code, as well as my conduct.
Let me know what is required of me to move forward.
Kind Regards,
Keith
--
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
[email protected].
For more options, visit
https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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
[email protected].
For more options, visit
https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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 [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/_K6gYSCupj0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
