Indicate where artifacts are going to and comming from in the log
Since we added:
- Support for multiple artifact caches defined in project.conf
- Support for junctions / multiple projects in one session
It's now become unclear where artifacts are coming from when being pulled, or where they are going to when they are being pushed.
Instead, I still see in the master log, messages such as:
[--:--:--][03cd65a7][ push:element.bst] START Pushing Artifact
...
[00:00:06][03cd65a7][ push:element.bst] SUCCESS Pushing Artifact
We need to include the urls here.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
- Show closed items
Link issues together to show that they're related.
Learn more.
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Tristan Van Berkom added Logging and removed Frontend labels
- Tom Coldrick mentioned in merge request !518 (closed)
mentioned in merge request !518 (closed)
- Javier Jardón assigned to @Qinusty
assigned to @Qinusty
The current state of logging in the area surrounding this issue looks like this:
[--:--:--][edf7fff5][ push:libhello.bst ] START CAS-interaction/libhello/edf7fff5-push.18521.log [--:--:--][edf7fff5][ push:libhello.bst ] START Pushing artifact [--:--:--][edf7fff5][ push:libhello.bst ] INFO Pushed artifact edf7fff5 [00:00:00][edf7fff5][ push:libhello.bst ] SUCCESS Pushing artifact [00:00:00][edf7fff5][ push:libhello.bst ] SUCCESS CAS-interaction/libhello/edf7fff5-push.18521.log ... [--:--:--][72f8f716][ push:hello.bst ] START CAS-interaction/hello/72f8f716-push.18604.log [--:--:--][72f8f716][ push:hello.bst ] START Pushing artifact [--:--:--][72f8f716][ push:hello.bst ] INFO Pushed artifact 72f8f716 [00:00:00][72f8f716][ push:hello.bst ] SUCCESS Pushing artifact [00:00:00][72f8f716][ push:hello.bst ] SUCCESS CAS-interaction/hello/72f8f716-push.18604.log
As a suggested solution, Perhaps we want something similar to the following:
[--:--:--][edf7fff5][ push:libhello.bst ] START CAS-interaction/libhello/edf7fff5-push.18521.log [--:--:--][edf7fff5][ push:libhello.bst ] START Pushing artifact -> https://localhost:11001 [--:--:--][edf7fff5][ push:libhello.bst ] INFO Pushed artifact edf7fff5 [00:00:00][edf7fff5][ push:libhello.bst ] SUCCESS Pushing artifact [00:00:00][edf7fff5][ push:libhello.bst ] SUCCESS CAS-interaction/libhello/edf7fff5-push.18521.log ... [--:--:--][72f8f716][ push:hello.bst ] START CAS-interaction/hello/72f8f716-push.18604.log [--:--:--][72f8f716][ push:hello.bst ] START Pushing artifact -> https://localhost:11001 [--:--:--][72f8f716][ push:hello.bst ] INFO Pushed artifact 72f8f716 [00:00:00][72f8f716][ push:hello.bst ] SUCCESS Pushing artifact [00:00:00][72f8f716][ push:hello.bst ] SUCCESS CAS-interaction/hello/72f8f716-push.18604.log
- Qinusty mentioned in merge request !553 (merged)
mentioned in merge request !553 (merged)
- Tristan Van Berkom mentioned in commit 6b82e476
mentioned in commit 6b82e476
- Tristan Van Berkom mentioned in commit 1d36df25
mentioned in commit 1d36df25
- Tristan Van Berkom closed via merge request !553 (merged)
closed via merge request !553 (merged)
- Tristan Van Berkom closed via commit 6b82e476
closed via commit 6b82e476
- Tristan Van Berkom mentioned in commit 364706f3
mentioned in commit 364706f3
Please register or sign in to reply