Well there is one flaky test on master, so we may need to either ignore the
flaky test or see about fixing it
On Wed 11 Jan 2017 at 00:10, Christian Schulte wrote:
> Am 01/11/17 um 00:52 schrieb Stephen Connolly:
>
> > Currently always running against the master branch of integration
> tests...
Am 01/11/17 um 00:52 schrieb Stephen Connolly:
> Currently always running against the master branch of integration tests...
Good to know. So the IT failure for that job is due to the missing
update to the IT (update to the core makes an existing IT fail). Thanks.
Currently always running against the master branch of integration tests...
the Jenkins plugin with resolving matching branches is not released yet
On Tue 10 Jan 2017 at 23:42, Christian Schulte wrote:
> Am 01/09/17 um 23:53 schrieb Stephen Connolly:
>
> > Yes. And the branch job will be deleted
Am 01/09/17 um 23:53 schrieb Stephen Connolly:
> Yes. And the branch job will be deleted automatically after you delete the
> branch (we can set an orphaned item strategy if we want to keep them around
> for a while)
Hi,
can you please take a look at the maven-jenkinsfile/MNG-5958 job. Did it
rea
Yes. And the branch job will be deleted automatically after you delete the
branch (we can set an orphaned item strategy if we want to keep them around
for a while)
On Mon 9 Jan 2017 at 22:44, Christian Schulte wrote:
> Am 01/09/17 um 23:36 schrieb Stephen Connolly:
>
> > Yes, every branch that h
Am 01/09/17 um 23:36 schrieb Stephen Connolly:
> Yes, every branch that has the Jenkinsfile will automatically get its own
> branch job build within 15 minutes of being pushed.
>
> (It would be faster - i.e. 5s after the push - but until I don't want to
> pester infra to upgrade Jenkins until I ha
Yes, every branch that has the Jenkinsfile will automatically get its own
branch job build within 15 minutes of being pushed.
(It would be faster - i.e. 5s after the push - but until I don't want to
pester infra to upgrade Jenkins until I have got some stability in the
branch-api 2.0.x series)
Th
Am 01/09/17 um 22:44 schrieb Stephen Connolly:
> Can we stage this logical set of changes on the same branch before merging
> to master (so we know we have a clean test run on the
> https://builds.apache.org/job/maven-jenkinsfile/ branch build)
What's this Jenkinsfile about? Does it mean whenever
Can we stage this logical set of changes on the same branch before merging
to master (so we know we have a clean test run on the
https://builds.apache.org/job/maven-jenkinsfile/ branch build)
On Mon 9 Jan 2017 at 21:41, Christian Schulte wrote:
> Am 01/09/17 um 21:03 schrieb Michael Osipov:
>
>
Am 01/09/17 um 21:03 schrieb Michael Osipov:
> Am 2017-01-09 um 19:58 schrieb Stephen Connolly:
>> If the commit mentions all the issues, e.g. [MNG-1235, MNG-4568] there
>> should be reasonable tracking... but if you feel more confident with one
>> issue per commit I see no issue with that either
>
Am 2017-01-09 um 19:58 schrieb Stephen Connolly:
If the commit mentions all the issues, e.g. [MNG-1235, MNG-4568] there
should be reasonable tracking... but if you feel more confident with one
issue per commit I see no issue with that either
Personally, yes. I have seen comments from users on i
If the commit mentions all the issues, e.g. [MNG-1235, MNG-4568] there
should be reasonable tracking... but if you feel more confident with one
issue per commit I see no issue with that either
On Mon 9 Jan 2017 at 18:51, Michael Osipov wrote:
> Am 2017-01-09 um 16:13 schrieb Christian Schulte:
>
Am 2017-01-09 um 16:13 schrieb Christian Schulte:
Hi,
there have been various issues in JIRA regarding the launcher scripts.
Is it possible to squash all those commits into one and then mention all
JIRA issues in the commit message so that the commit is added to each
JIRA issue? Last time I did
I suggest one of you creates a branch and you flatten each of your
sequential commits into that branch one at a time. The person to create the
branch should be the first commit and then proceed in order.
Or if you all agree then one of you can just create a branch with the final
end game committin
Am 01/09/17 um 16:13 schrieb Christian Schulte:
> Hi,
>
> there have been various issues in JIRA regarding the launcher scripts.
> Is it possible to squash all those commits into one and then mention all
> JIRA issues in the commit message so that the commit is added to each
> JIRA issue? Last tim
If you did all the commits, then that is fine.
If you are effectively squashing the work of others, you'll probably need
to at least retain their commits with the authorship
On 9 January 2017 at 15:13, Christian Schulte wrote:
> Hi,
>
> there have been various issues in JIRA regarding the launc
Hi,
there have been various issues in JIRA regarding the launcher scripts.
Is it possible to squash all those commits into one and then mention all
JIRA issues in the commit message so that the commit is added to each
JIRA issue? Last time I did this I think Jenkins was able to add
comments to all
17 matches
Mail list logo
