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

Resource filtering fails when run from Hudson

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: PC, OS: Solaris

      This morning, we upgraded to 1.306

      We had some shell scripts being filtered during packaging. A few properties in
      them (like installation directory) were being filtered and leaving things such
      as CLASSPATH and JAVA_HOME alone (because they are not defined properties).

      As of today, those get filtered to match the values on the Hudson server. We can
      not replicate this from the command-line, even from the same machine. It only
      happens when run from within Hudson.

      We were using the maven-assembly-plugin to do the filtering. The
      maven-resources-plugin is doing the same thing.... but only from Hudson.

            Unassigned Unassigned
            malachid malachid
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: