You will probably all receive notifications like Janek below.
In fact it should not occur again in your personal repo after applying
today's changes to [1].
Provided that you don't touch master branch.
You can even disable CI completely so you are not annoyed by pipeline
failure
I am so lost that I don't know what questions to ask :)
Bruno Chareyre said: (by the date of Thu, 17 Jan 2019 18:12:08 +0100)
> On 1/17/19 5:53 PM, Jerome Duriez wrote:
> > it's maybe time to ask what does YADE development (if not "we") may
> > expect as investment from Grenoble "in
On 1/17/19 5:53 PM, Jerome Duriez wrote:
it's maybe time to ask what does YADE development (if not "we") may
expect as investment from Grenoble "in exchange" ?
Who is expecting something, from who, in exchange of what? You lost me,
sorry. :)
Bruno
Haha, don't worry.
No I didn't do anything but that's just expected.
You enabled shared runners here:
https://gitlab.com/cosurgi/trunk/settings/ci_cd
.
Those shared runners are provided by gitlab.com, for free. But they lack
power (timeout) and RAM to build yade with make -j12. ;)
There is my
Hi Bruno,
Thank you for everything.
It was a reason for new ways of doing things (the merge requests, in
particular), it's maybe time to ask what does YADE development (if not
"we") may expect as investment from Grenoble "in exchange" ?
Good hopes to maintain all that we have in spite of
Hi there,
The repository is functional at:
https://gitlab.com/yade-dev/trunk
For using gitlab you can read the updated doc page
https://yade-dev.gitlab.io/trunk/github.html#yade-github-label
As soon as you have a gitlab account let me know your login name so I
can add you to the project.
I
Yeah, I think next weekend is ok. Unless we run into some problems :)
Bruno, we will have a nice opportunity to check merge requests in gitlab. I
have just created a new branch in my repo:
https://gitlab.com/cosurgi/trunk/commits/all-examples-must-work
So we will try merging it next week ! :)
7 matches
Mail list logo
