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

Can't properly create Emoji Only Jobs (╯°□°)╯︵ ┻━┻

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Duplicate
    • core
    • Jenkins 2.190.1
    • 2.196

    Description

      Tried to create job named "(╯°□°)╯︵ ┻━┻"

      Expected results : Would move to job configuration page.
      Actual results : (java stack trace)

      Now, if I create a similar job, but I use some leading ascii text, eg:
      Tried to create job named : "TBF (╯°□°)╯︵ ┻━┻"
      Expected results : Would move to job configuration page.
      Actual results : Moved to job configuration page.

      If I inspect the JENKINS_HOME/jobs directory, the (╯°□°)╯︵ ┻━┻ directory does get created, but I am unable to configure this through the GUI.

      Attachments

        Issue Links

          Activity

            mhall4 Matthew Hall added a comment - - edited
            [root@jmtest jobs]# cd (╯°□°)╯︵\ ┻━┻/
             [root@jmtest (╯°□°)╯︵ ┻━┻]# ls
             builds config.xml
             [root@jmtest (╯°□°)╯︵ ┻━┻]# ls -al
             total 32
             drwxr-xr-x 3 jenkins jenkins 4096 Oct 3 11:19 .
             drwxr-xr-x 405 jenkins jenkins 20480 Oct 3 11:19 ..
             drwxr-xr-x 2 jenkins jenkins 4096 Oct 3 11:19 builds
             rw-rr- 1 jenkins jenkins 206 Oct 3 11:19 config.xml
             [root@jmtest (╯°□°)╯︵ ┻━┻]# more config.xml 
             <?xml version='1.1' encoding='UTF-8'?>
             <flow-definition plugin="workflow-job@2.35">
             <keepDependencies>false</keepDependencies>
             <properties/>
             <triggers/>
             <disabled>false</disabled>
             </flow-definition>
             [root@jmtest (╯°□°)╯︵ ┻━┻]# ls builds
             legacyIds
             [root@jmtest (╯°□°)╯︵ ┻━┻]# pwd
             /home/jenkins/jobs/(╯°□°)╯︵ ┻━┻
            mhall4 Matthew Hall added a comment - - edited [root@jmtest jobs]# cd (╯°□°)╯︵\ ┻━┻/ [root@jmtest (╯°□°)╯︵ ┻━┻]# ls builds config.xml [root@jmtest (╯°□°)╯︵ ┻━┻]# ls -al total 32 drwxr-xr-x 3 jenkins jenkins 4096 Oct 3 11:19 . drwxr-xr-x 405 jenkins jenkins 20480 Oct 3 11:19 .. drwxr-xr-x 2 jenkins jenkins 4096 Oct 3 11:19 builds rw-rr- 1 jenkins jenkins 206 Oct 3 11:19 config.xml [root@jmtest (╯°□°)╯︵ ┻━┻]# more config.xml <?xml version='1.1' encoding='UTF-8'?> <flow-definition plugin="workflow-job@2.35"> <keepDependencies>false</keepDependencies> <properties/> <triggers/> <disabled>false</disabled> </flow-definition> [root@jmtest (╯°□°)╯︵ ┻━┻]# ls builds legacyIds [root@jmtest (╯°□°)╯︵ ┻━┻]# pwd /home/jenkins/jobs/(╯°□°)╯︵ ┻━┻
            mhall4 Matthew Hall added a comment - - edited

            Also, to use another example. If I create :

            See No Evil :see no evil monkey: 

            as a job, this works.

            If I try to create it as :

            :see no evil monkey: See No Evil

            It fails. Seems to be related to the emoji being the leading part of the job name.

            (I can't use the actual monkey, due to Jira not taking it :
            It fails.][numvalue,null][updated,2019-10-03 18:41:35.326] (SQL Exception while executing the following:UPDATE jiraaction SET issueid=?, AUTHOR=?, actiontype=?, actionlevel=?, rolelevel=?, actionbody=?, CREATED=?, UPDATEAUTHOR=?, UPDATED=?, actionnum=? WHERE ID=? (Incorrect string value: '\xF0\x9F\x99\x88: ...' for column 'actionbody' at row 1))
            )

            mhall4 Matthew Hall added a comment - - edited Also, to use another example. If I create : See No Evil :see no evil monkey: as a job, this works. If I try to create it as : :see no evil monkey: See No Evil It fails. Seems to be related to the emoji being the leading part of the job name. (I can't use the actual monkey, due to Jira not taking it : It fails.] [numvalue,null] [updated,2019-10-03 18:41:35.326] (SQL Exception while executing the following:UPDATE jiraaction SET issueid=?, AUTHOR=?, actiontype=?, actionlevel=?, rolelevel=?, actionbody=?, CREATED=?, UPDATEAUTHOR=?, UPDATED=?, actionnum=? WHERE ID=? (Incorrect string value: '\xF0\x9F\x99\x88: ...' for column 'actionbody' at row 1)) )
            jesse_houghton Jesse Houghton added a comment - - edited

            Hi mhall4 I believe this has been fixed as of weekly release 2.196 - It looks like it's marked for back porting in 2.190.2 (The next version of the LTS version)  I've added a link this Jira to the previous issue.

             

            Here's results from a local test on the latest code stream:

            jesse_houghton Jesse Houghton added a comment - - edited Hi mhall4 I believe this has been fixed as of weekly release 2.196 - It looks like it's marked for back porting in 2.190.2 (The next version of the LTS version)  I've added a link this Jira to the previous issue.   Here's results from a local test on the latest code stream:
            llamahunter Richard Lee added a comment -

            they may appear in the job view, but can you click on them to configure them?

            llamahunter Richard Lee added a comment - they may appear in the job view, but can you click on them to configure them?

            llamahunter I can click on the job name, click configure, and then save. Is that what you mean? Apologies if I'm missing something obvious

             

             

            jesse_houghton Jesse Houghton added a comment - llamahunter I can click on the job name, click configure, and then save. Is that what you mean? Apologies if I'm missing something obvious    
            llamahunter Richard Lee added a comment -

            Yup!  We were able to see the emoji jobs in the Job view, but clicking on them to get details caused the stack trace.  Your image above didn't show the drill down that we saw causing failures.

            Anyway, sounds like its fixed. 

            llamahunter Richard Lee added a comment - Yup!  We were able to see the emoji jobs in the Job view, but clicking on them to get details caused the stack trace.  Your image above didn't show the drill down that we saw causing failures. Anyway, sounds like its fixed. 
            oleg_nenashev Oleg Nenashev added a comment -

            Closing as a duplicate

            oleg_nenashev Oleg Nenashev added a comment - Closing as a duplicate

            People

              Unassigned Unassigned
              mhall4 Matthew Hall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: