feat: pipeline starts without creating a trigger

[vfried]

The pipeline starts now without creating a trigger.

To test fork a project and go to CI/CD => pipelines in gitlab and you will see that after forking a project there is a pipeline running.

For some reason it fails for old projects. I think in the future we can after redirect offer the option to restart failed pipelines (Like for Knowledge Graph).

Closes #511

[rokroskar]

For some reason it fails for old projects.

how old is old?

[vfried]

For some reason it fails for old projects.

how old is old?

I'm not sure, I left the office and couldn't finish investigating on the issue. I was planning on trying to check tomorrow what's going on.

[vfried]

For some reason it fails for old projects.

how old is old?

I'm not sure, I left the office and couldn't finish investigating on the issue. I was planning on trying to check tomorrow what's going on.

I realised some forks where failing because I was trying to start the pipeline before the project was fully forked. For this reason I now check project import status as stated here: https://docs.gitlab.com/ee/api/project_import_export.html#import-status

I set up a timer and try 10 times to see if the pipeline is ready to be run or not (So far it was always successful on the 1st time).

I think the older projects where taking longer to being fetched or something and this is why they where failing.

[lorenzo-cavazzi]

--

[lorenzo-cavazzi]

Now everything works fine, great!

---

A note on the modal

I minor suggestion would be to add stronger feedback to the user while the fork is ongoing. An example would be

• disable the 2 buttons while forking
• add a short sentence like forking project... before the spinning wheel.

Since it's a minor detail, feel free to ignore this suggestion and merge if you think it's not particularly useful 🙂

[ciyer]

I tried it out; the feature is very nice and the code looks good! I agree, though, that the feedback on the modal dialog should be more explicit: as you suggest, the fork and cancel buttons should be disabled and a short description of what's going on should be there.

[vfried]

I tried it out; the feature is very nice and the code looks good! I agree, though, that the feedback on the modal dialog should be more explicit: as you suggest, the fork and cancel buttons should be disabled and a short description of what's going on should be there.

Done... now buttons are disabled and there is a message as in the following image when the project is being forked. (The image doesn't show the disabled buttons but they are disabled)

[lorenzo-cavazzi]

Looks good to me now! Very useful feature