Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51750

Config file provider doesn't always copy file to pipeline

    Details

    • Similar Issues:

      Description

      I have several pipelines depending on a config file to be injected by the plugin using its fileId.

      Inside the pipeline I copy and use the injected config file by its name, which is `.env`.

      However, I noticed that sometimes, in high probability, the file isn't copied into the workspace.

      I print the workspace files and specifically check for the `.env` file in the beginning of the pipeline, and sometimes the file is just not copied there, even though in all those times the plugin prints that it has copied the file to the correct path.

       

      I'm using the latest release of this plugin.

      I thought it might be related to the fact the file starts with a dot, but even without it the problem still occurs.

       

      The result is that I have to build every pipeline project several times until the file successfully copied into workspace.

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            It is hard to process it without plugin versions and Pipeline script examples

            Show
            oleg_nenashev Oleg Nenashev added a comment - It is hard to process it without plugin versions and Pipeline script examples
            Hide
            aviadm Aviad M added a comment -

            Oleg Nenashev

            Plugin version: 2.18

            Jenkins version: 2.89

            The code is pretty simple, I wrap it up with the `configFileProvider` call with the correct `fileId` and then calls a shell script with `sh` command which expects the file to be present, searching it on filesystem by it's name.

             

             

            Show
            aviadm Aviad M added a comment - Oleg Nenashev Plugin version: 2.18 Jenkins version: 2.89 The code is pretty simple, I wrap it up with the `configFileProvider` call with the correct `fileId` and then calls a shell script with `sh` command which expects the file to be present, searching it on filesystem by it's name.    

              People

              • Assignee:
                domi Dominik Bartholdi
                Reporter:
                aviadm Aviad M
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: