Hi,
it's almost a week late, but I've just requested administrative Jenkins
access for Harry, David and myself, so we should be able to make changes to
the CI job without needing to file a JIRA issue. Right now our Jenkins job
uses JDK 6 (latest), Maven 3.0.4 and the source is grabbed from the
Looks good. Looks like Jenkins is building now.
With Git we may need to update Jenkins to build different branches, e.g.
develop / master.
Can we get "Configuration" access to the "JSPWiki" job in Jenkins? Is this
something we get grant each other or do we need to create an INFRA ticket?
I just entered https://issues.apache.org/jira/browse/INFRA-12628 to ask the
infra team to reflect the svn2git migration in our Jenkins job.
regards,
Harry
On 16 September 2016 at 16:45, Harry Metske wrote:
> Sounds like a good plan!
>
> On 16 September 2016 at 13:07,
Sounds like a good plan!
On 16 September 2016 at 13:07, David Vittor wrote:
> This looks good. I've had a play with it.
>
> Although I think the next thing is we have to work out how branches and
> pull requests will work.
>
> I'm assuming we will start using feature
This looks good. I've had a play with it.
Although I think the next thing is we have to work out how branches and
pull requests will work.
I'm assuming we will start using feature branches, were we will have a
different branch for each JIRA ticket.
Then we need to merge these branches into some
Hi,
our svn to git migration is done.
New resources:
browse git repo :
https://git-wip-us.apache.org/repos/asf?p=jspwiki.git;a=summary
git clone url : https://git-wip-us.apache.org/repos/asf/jspwiki.git
github mirror: https://github.com/apache/jspwiki
I made some quick changes on our wiki to
OK, asfinfra already has a model JIRA for this (SVN->GIT Migration), these
fields must be entered, agree with these values ? :
Git Notification Mailing List : comm...@jspwiki.apache.org
Git Repository Name : jspwiki
Git Repository Import Path :
Hi,
+1 here too
br,
juan pablo
El 20 ago. 2016 5:14 a. m., "David Vittor" escribió:
> Oops on mobile. That was meant to be +1. :)
> On 20/08/2016 1:13 PM, "David Vittor" wrote:
>
> > ±1 for git from me also. I use this at work now also, so am familiar
Oops on mobile. That was meant to be +1. :)
On 20/08/2016 1:13 PM, "David Vittor" wrote:
> ±1 for git from me also. I use this at work now also, so am familiar with
> it.
>
> Cheers,
> David V
> On 20/08/2016 11:23 AM, "Dave Koelmeyer" co.nz>
±1 for git from me also. I use this at work now also, so am familiar with
it.
Cheers,
David V
On 20/08/2016 11:23 AM, "Dave Koelmeyer"
wrote:
> On a related note, if this goes ahead perhaps someone (at some stage)
> can summarise some of the pros of switching
On a related note, if this goes ahead perhaps someone (at some stage)
can summarise some of the pros of switching to git and I can create an
announcement blog post.
Cheers,
Dave
On 20/08/16 06:01, Jürgen Weber wrote:
> Hi,
>
> I am for git, too.
> But is there an apache.org repository?
>
>
11 matches
Mail list logo