One thing I noticed since migration. Our build is marked as failed on github due to a commit on failing PR. i don’t think it was the case before. Regards
On Thursday, June 13, 2019, Vladimir Sitnikov <[email protected]> wrote: > Vladimir> https://github.com/apache/jmeter > Philippe>Isn't it > > Just in case: https://github.com/apache/jmeter (with master=778016e..) is > a > **result** of cleanup v2.2.0 > The cleanup script is > https://github.com/vlsi/jmeter-git-cleanup/tree/v2.2.0/clean_fork (you > just use it as is, and you do not un-comment lines unless you are > absolutely sure) > > PS. Are there Windows users? We might need Windows-based *.bat script, > however as nobody asks for that I just ignore it. > > >Yes , I had used 2.1.1 > >Shall I run 2.2.0 on my current fork ? > > Do you have a backup? > If you do, I would recommend get that and run 2.2.0 on top of it. > > Alternative option is to run 2.2.0 on top of "after cleanup v2.1.1" repo. > Theoretically it should produce the same result (the only difference is > CRLF issues, so cleanup 2.2.0 should work after 2.1.1 just fine). > However I would be on a safe side and just ran v2.2.0 on top of your fork. > At the end of the day, I have not tested all the possible cleanup execution > orders. > > Note: I executed v2.2.0 in my own fork and it was just fine (I develop > Gradle migration in that fork, and there are lots of historical branches as > well). > I did not have to clone-reclone that from github. I just copied repo in a > side folder, copied cleanup scripts there and that was it. > > Vladimir >
