$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>to be continuous - How to use artifacts from previous stage in TBC semantic release componenet publish stage? - Stack Overflow|Programmer puzzle solving

Programmer puzzle solving

    最新消息：Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)
    你的位置： HOME>matter>to be continuous - How to use artifacts from previous stage in TBC semantic release componenet publish stage? - Stack Overflow

    to be continuous - How to use artifacts from previous stage in TBC semantic release componenet publish stage? - Stack Overflow

    matteradmin15PV0评论

    I am trying to pass an file artifact from my build stage to the TBC semantic release component publish stage so that I can rename it and add it as a release asset.

    When I run my pipeline it shows that the artifact was correctly saved in the build stage. In the publish stage with the semantic release job it fails because it cannot find the artifact file that was saved in the build stage.

    Is it possible to make the artifacts from previous stages usable in the semantic release job?

    I have checked that the previous stage did save the artifact by looking at the Gitlab pipeline viewer.

    I have tried another TBC component and it correctly uses the previous stage artifacts. The gitlab ci package TBC component correctly loads the artifacts from the previous stage as expected. Below is the portion of the log where this happens:

    Downloading artifacts 00:01
Downloading artifacts for build-pdf (8367422461)...

    But if I look at the semantic release job log the artifact download does not occur.

    continue to browse articles about articles of

    Articles related to this article

    Post a comment

    comment list (0)

    1. No comments so far