Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitLab pages GitLab CI job hangs #170

Closed
xlxs4 opened this issue May 15, 2020 · 5 comments
Closed

GitLab pages GitLab CI job hangs #170

xlxs4 opened this issue May 15, 2020 · 5 comments

Comments

@xlxs4
Copy link

xlxs4 commented May 15, 2020

Reproducing

Have a template set up with every default as it is and GitLab pages the only plugin. Push to GitLab and wait. After test and the initial pages job successfully conclude, a new external job spawns named pages:deploy. The job gets retried quickly (sub-minute quickly), this occurs 2 or 3 more times with the end result being something like this:

image

Description

GitLab CI jobs triggered after pushing templates generated hang (indefinitely?).
After some debugging and playing around, it seems that only the GitLab pages deployment is problematic. All other plugins (AppVeyor, Coverage, GitLab CI...) seem to work as intended. Same issue occurs while using both latest (not stable) 0.6.4 release and in stable 0.6.3. I haven't tried passing additional assets to Documenter while creating the template, I went for the default None value. I also tried to mimic what Papp proposed in his "demo repo" here to no avail.

Of course, this might not be relevant to PkgTemplates, and GitLab could be at fault. Specifically, it could be related to other similar issues (or even to yesterday's incidents)

Let me know if you need any additional info.
Sorry in advance if I'm being stupid with this, I'm a novice 😄

@christopher-dG
Copy link
Member

Can you try it on master branch? (The bit about 0.6.3 being the stable release is outdated, but there are no changes to GitLab in 0.6.4 anyways)

@xlxs4
Copy link
Author

xlxs4 commented May 15, 2020

I did, same results

@christopher-dG
Copy link
Member

Link to the repo please?

@xlxs4
Copy link
Author

xlxs4 commented May 15, 2020

It was a test repo so I could experiment with the package, so I made one anew and reproduced... or so I thought :P
It works now as intended. I guess it's on GitLab's side
Feel free to close and thanks for the timely assistance

@christopher-dG
Copy link
Member

Sounds good 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants